| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
behavior of malloc and realloc when request size is 0. Fix escape
sequence recognizer so that only valid 3-digit octal sequences are
treated as escape sequences ... isdigit() is not a correct test.
|
|
|
|
|
|
| |
rule into the rule.sql since it affects the latter if run in paralell.
Jan
|
| |
|
|
|
|
|
|
|
|
| |
rule split the query into one INSERT and one UPDATE where the UPDATE
then hit's the just created row without modifying the key fields again.
In this special case, the new key slipped in totally unchecked.
Jan
|
|
|
|
|
| |
a special character in regexes, but it is for LIKE, so NOT LIKE 'pg_%'
is incorrect. Need NOT LIKE 'pg\_%'.
|
|
|
|
|
| |
in libpgtcl's lo_read/lo_write commands. Also, deal correctly with
failure return from lo_read(). ljb and Tom Lane.
|
|
|
|
|
|
|
|
|
| |
offered for completion only when the input-so-far is at least 'pg_'.
This seems to be the best compromise behavior emerging from yesterday's
discussion. While at it, refactor code to eliminate repetitive use of
nearly identical queries, which was exceedingly tedious to maintain.
Also const-ify code more thoroughly in hopes of moving constant data into
text segment, and remove unnecessary length limit on queries.
|
|
|
|
| |
Per example from Kumar, 30-Oct-03.
|
| |
|
| |
|
|
|
|
|
|
| |
ACL array, and force languages to be treated as owned by the bootstrap
user ID. (pg_language should have a lanowner column, but until it does
this will have to do as a workaround.)
|
|
|
|
| |
Per example from Ian Barwick, 28-Oct-03.
|
|
|
|
|
| |
FSM data has to be both moved down and compressed. Per report from
Dror Matalon.
|
|
|
|
| |
automatically delete cursors
|
|
|
|
|
|
|
|
| |
"schema." has been typed. This allows readline to complete subsequent
characters immediately if all relations in the target schema start with
the same prefix. This actually worked before, but I unintentionally
broke it a few days ago.
Also, make completion schema-aware for GRANT, REVOKE, VACUUM.
|
|
|
|
| |
from Johan Henselmans.
|
|
|
|
| |
the pg_catalog schema. Per bug report some months back from Jochem van Dieten.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make a LOT of fixes to syscat.source to:
* Set search_path properly (and reset it)
* Add schema name to all results
* Add schema name to ORDER BY first
* Make checks for user-defined objects match reality
* format_type all type names
* Respect attisdropped
* Change !~ to 'not like' since it's more standard
Christopher Kings-Lynne
|
|
|
|
| |
Hiroshi Saito
|
| |
|
| |
|
| |
|
|
|
|
| |
Add m68k to linux port.
|
|
|
|
|
|
| |
0.0/0.0. That option appears to affect the regression test result as well.
The compiler documentation doesn't recommend -O4 for universal use, so
let's stick to the conservative -O (== -O2) by default.
|
| |
|
| |
|
|
|
|
| |
option -fno-strict-aliasing is available.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Avoids warnings from newer bisons.
|
|
|
|
|
| |
and add binary send/receive functions. Fix some other grottiness such
as failure to mark the C functions STRICT.
|
|
|
|
|
|
| |
are properly schema-qualified.
Christopher Kings-Lynne
|
|
|
|
| |
LLONG_MIN. One example is AIX, per report from Andreas.
|
|
|
|
| |
on Windows; per complaint from Andreas that it breaks AIX build.
|
|
|
|
|
|
| |
against a 7.0 server.
Christopher Kings-Lynne
|
| |
|
|
|
|
| |
the user is confused about whether -f is input or output file.
|
|
|
|
|
|
|
|
|
|
| |
subquery that didn't previously have one. We have traditionally made
the caller of ResolveNew responsible for updating the hasSubLinks flag
of the outermost query, but this fails to account for hasSubLinks in
subqueries. Fix ResolveNew to handle this. We might later want to
change the calling convention of ResolveNew so that it can fix the
outer query too, simplifying callers. But I went with the localized
fix for now. Per bug report from J Smith, 20-Oct-03.
|
|
|
|
| |
behavior reported by Martin Marques.
|
| |
|
|
|
|
|
|
|
|
|
| |
to ensure any needed compiler support routines are included. This is
arguably appropriate on *every* gcc platform, but for the moment I'll take
the conservative approach of only doing it on a platform where it's
provably useful. Per complaint from Heiko Lehmann, 13-Feb-03, as well
as personal experience --- contrib/pgstattuple has never worked for me,
but it does now.
|
| |
|