| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
| |
- is not initialized to 1 (at least in the WIN_32 code I started with!)
Claudio Natoli
|
|
|
|
| |
Other cleanups as discussed.
|
|
|
|
|
|
|
| |
This is his original version with a binary rmdir() we might need in the
future.
I will commit an update version with cleanups shortly.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the 'strategy map' code, which was a large amount of mechanism
that no longer had any use except reverse-mapping from procedure OID to
strategy number. Passing the strategy number to the index AM in the
first place is simpler and faster.
This is a preliminary step in planned support for cross-datatype index
operations. I'm committing it now since the ScanKeyEntryInitialize()
API change touches quite a lot of files, and I want to commit those
changes before the tree drifts under me.
|
|
|
|
| |
RENAME TO option.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
they do not prevent the postmaster from deleting the shmem segment during
a post-backend-crash restart cycle. Per recent discussion.
|
|
|
|
|
| |
else it cannot be used to handle failures detected during WAL replay.
Fortunately this flag isn't actually enforced yet, but get it right.
|
|
|
|
| |
like the next higher one.
|
|
|
|
|
|
|
|
|
|
|
| |
regression=# select 1 from tenk1 ta cross join tenk1 tb for update;
ERROR: no relation entry for relid 3
7.3 said "SELECT FOR UPDATE cannot be applied to a join", which was better
but still wrong, considering that 7.2 took the query just fine. Fix by
making transformForUpdate() ignore JOIN and other special RTE types,
rather than trying to mark them FOR UPDATE. The actual error message now
only appears if you explicitly name the join in FOR UPDATE.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
port to be specified in test cases
|
| |
|
| |
|
|
|
|
| |
platform-dependent results, as per example from Larry Rosenman.
|
|
|
|
|
| |
limit on the number of simultaneous connections. Andrew Dunstan, with
review by Tom Lane.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Neil Conway.
|
| |
|
|
|
|
|
|
|
|
|
| |
process the command as though it were issued by the object owner.
This prevents creating weird scenarios in which the same privileges
may appear to flow from different sources, and ensures that a superuser
can in fact revoke all privileges if he wants to. In particular this
means that the regression tests work when run by a superuser other than
the original bootstrap userid. Per report from Larry Rosenman.
|
|
|
|
|
|
| |
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.
|