Age | Commit message (Collapse) | Author |
|
Grumble.
|
|
the first one listed in a query. Per request from Oleg.
|
|
|
|
It pfree() wrong pointer.
|
|
in ruleutils output. The previous partial parenthesization was a hack
to get around grammar restrictions that have since been fixed; and as
Sam O'Connor pointed out, there were cases where it didn't work.
|
|
(Already fixed in current, but need a patch for 7.2.2.)
|
|
Patch from Teodor Sigaev.
|
|
reference count. This avoids leaving dangling pointers around, as in
recent bug report against sequences (bug# 671).
|
|
be smarter about parentheses in read_sql_construct(). Sigh.
|
|
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.
|
|
--nonexistingoption).
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>.
|
|
|
|
see changes made by the transaction itself.
|
|
Fix PQescapeBytea/PQunescapeBytea so that they handle bytes > 0x7f.
This is necessary for mulibyte character sequences.
See "[HACKERS] PQescapeBytea is not multibyte aware" thread posted around
2002/04/05 for more details.
|
|
wrapped-around databases. The unvacuumed databases might be fine, or
they might not, but things will definitely not be fine if we remove the
wrong CLOG segments. Per trouble report from Gary Wolfe, 1-Apr-2002.
|
|
|
|
|
|
|
|
|
|
|
|
lower subscript bounds change.
|
|
Will be patched separately but equivalently in HEAD for 7.3.
|
|
per recent pghackers discussion: force a new WAL record at first nextval
after a checkpoint, and ensure that xlog is flushed to disk if a nextval
record is the only thing emitted by a transaction.
|
|
Problem noted by Fernando Nasser.
|
|
three-or-more-way UNIONs, as per example from Josh Berkus. Cause is a
fragile assumption that one tlist's entries will exactly match another.
Restructure code to make that assumption a little less fragile.
|
|
Fix bug in extract/date_part for milliseconds/miscroseconds and
timestamp/timestamptz combo. Now extract/date_part returns
seconds*1000 or 1000000 + fraction part as the manual stats.
regression test are also fixed.
See the thread in pgsql-hackers:
Subject: Re: [HACKERS] timestamp_part() bug?
Date: Sat, 02 Mar 2002 11:29:53 +0900
|
|
|
|
Fix bug in COPY FROM when DELIMITER is not in ASCII range.
See pgsql-bugs/pgsql-hackers discussion "COPY FROM is not 8bit clean"
around 2002/02/26 for more details -- Tatsuo Ishii
|
|
primarily needed so that INSERTing a row still reports the row's OID
even when there are ON INSERT rules firing additional queries.
|
|
names. This is a temporary measure to allow backwards compatibility with
7.2 and earlier pg_dump. 7.2.1 and later pg_dump will double-quote mixed
case names in \connect. Once we feel that older dumps are not a problem
anymore, we can revert this change and treat \connect arguments as normal
SQL identifiers.
|
|
> and that the right fix is to make each of the subsequent calls be in
> this same pattern, not to try to emulate their nonsensical style.
Dominic J. Eidson
|
|
Fix a few apparently-wrong TZ vs DTZ declarations.
Same patch as added to HEAD.
|
|
In the mailing lists I found no informations.
See note for further informations.
Add missing AuthBlockSig.
regards Heiko
|
|
Also, 'fourty' -> 'forty'.
|
|
pghackers discussion.
|
|
Per Yoshinori Ariie's report.
|
|
|
|
originally created with, so that the set of visible tuples does not
change as a result of other activity. This essentially makes PG cursors
INSENSITIVE per the SQL92 definition. See bug report of 13-Feb-02.
|
|
This restores the Linux behavior to what it was in PG 7.0 and 7.1, and
causes other platforms to agree. (Other well-tested platforms like HPUX
were doing it this way already.) Per pghackers discussion over the past
month or so.
|
|
(backslash-r, backslash-n) for protection against newline-conversion
munging. In future we will also tweak COPY FROM, but this part of the
change should be backwards-compatible. Per pghackers discussion.
Also, update COPY reference page to describe the backslash conversions
more completely and accurately.
|
|
of pointers is required. Patch from Teodor Sigaev per pghackers
discussion. It's an ugly kluge but avoids forcing initdb; we'll put
a better fix into 7.3 or later.
|
|
|
|
inner indexscan (ie, one with runtime keys). ExecIndexReScan must
compute or recompute runtime keys even if we are rescanning in the
EPQ case. TidScan seems to have comparable problems. Per bug
noted by Barry Lind 11-Feb-02.
|
|
the CREATE DATABASE command right in pg_dump -C case.
|
|
crash on Solaris when over disk quota. Instead, report such failures
via elog(DEBUG).
|
|
|
|
Patch from sugita@sra.co.jp.
|
|
|
|
|
|
|