| Age | Commit message (Collapse) | Author |
|---|
|
is actively dangerous, per bug report from Ewald Geschwinde 14-May-02,
and several of the rest look suspicious to me. Since there is no longer
any significant value in retail pfree's in these functions, just get
rid of all of them for safety's sake.
|
|
integer datetimes. Thanks to Tom Lane for spotting the problem.
|
|
to C at run-time, and providing alternative output files for different
sort orders.
|
|
per report from sugita@sra.co.jp on Thu, 09 May 2002 11:57:51 +0900
(JST) at pgsql-patches list.
Illegal long options to pg_dump makes core on some systems, since it
lacks the last null sentinel of struct option array.
Attached is a patch made by Mr. Ishida Akio <iakio@pjam.jpweb.net>.
|
|
The code was not expecting to receive notice messages during the connection handshake.
|
|
|
|
underlying function; but cause psql's \do to show the underlying
function's comment if the operator has no comment of its own, to preserve
the useful functionality of the original behavior. Also, implement
COMMENT ON SCHEMA. Patch from Rod Taylor.
|
|
returns-set boolean field in Func and Oper nodes. This allows cleaner,
more reliable tests for expressions returning sets in the planner and
parser. For example, a WHERE clause returning a set is now detected
and complained of in the parser, not only at runtime.
|
|
some kibitzing from Tom Lane. Not everything works yet, and there's
no documentation or regression test, but let's commit this so Joe
doesn't need to cope with tracking changes in so many files ...
|
|
|
|
but the basic capability seems to work.
|
|
|
|
Re-add warning if the locale prevents LIKE-optimization. Done within
initdb now.
|
|
|
|
to reset session userid to the originally-authenticated name. Also,
relax SET SESSION AUTHORIZATION to allow specifying one's own username
even if one is not superuser, so as to avoid unnecessary error messages
when loading a pg_dump file that uses this command. Per discussion from
several months ago.
|
|
some of his own privileges.
|
|
in hopes of making erroneous usage more apparent. Per discussion 15-Apr.
|
|
where the tuple's xmin or xmax is older than the snapshot xmin. There
is no need to check it against snapshot xmax in that case.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As proof of concept, provide an alternate implementation based on POSIX
semaphores. Also push the SysV shared-memory implementation into a
separate file so that it can be replaced conveniently.
|
|
|
|
only if they would not be found without qualification given the current
search path, as per idea from Peter Eisentraut.
|
|
|
|
from Liam Stewart. Minor code cleanups also.
|
|
|
|
|
|
handled as special productions. This is needed to keep us honest about
user-schema type names that happen to coincide with system type names.
Per pghackers discussion 24-Apr. To avoid bloating the keyword list
too much, I removed the translations for datetime, timespan, and lztext,
all of which were slated for destruction several versions back anyway.
|
|
|
|
in gram.y can make use of the keywords.c string table, instead of having
their own copies of the keyword strings. This saves a few kilobytes and
more importantly eliminates an opportunity for cut-and-paste errors.
|
|
in the search path. (We might want to make these available as SQL
functions too, but I haven't done that yet.) Fix format_type to be
schema-aware.
|
|
binary case) already has. Needed for upcoming ruleutils change.
|
|
in parse error messages, not just the part scanned by the last flex rule.
For example,
select "foo" "bar";
used to draw
ERROR: parser: parse error at or near """
which was rather unhelpful. Now it gives
ERROR: parser: parse error at or near ""bar""
Also, error messages concerning bitstring literals and suchlike will
quote the source text at you, not the processed internal form of the literal.
|
|
PL/PgSQL grammar, which were causing warnings when used with Bison
1.35.
Neil Conway <neilconway@rogers.com>
|
|
see changes made by the transaction itself.
|
|
in presence of schemas.
|
|
|
|
I concluded that RENAME should require CREATE privilege on the namespace
as well as ownership of the table.
|
|
don't scribble on tuple returned by table scan.
|
|
|
|
|
|
|
|
gcc does not complain about this mistake, but other compilers do.
|
|
|
