| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
This first part of the background writer does no syncing at all.
It's only purpose is to keep the LRU heads clean so that regular
backends seldom to never have to call write().
Jan
|
| |
|
| |
|
|
|
|
|
|
| |
which had been unintentionally broken by recent changes to tighten up the
DateStyle rules for all-numeric date input. Add documentation and
regression tests for this, too.
|
|
|
|
|
|
|
|
|
| |
debug_shared_buffers = <seconds>
as per previous discussion.
Jan
|
|
|
|
|
| |
to try additional addresses returned from getaddrinfo() if the first one
fails at the bind() or connect() steps. Per yesterday's discussion.
|
| |
|
| |
|
|
|
|
| |
can terminate the bootstrap run.
|
|
|
|
| |
double or out-of-sequence output with child process.
|
|
|
|
|
|
| |
data directory. Also fix handling of error conditions associated with
data directory checking step (can't use a boolean to distinguish four
possible result states...)
|
|
|
|
|
|
|
| |
and the cache replacement strategy as well as a description of the
ARC algorithm and the special tailoring of that done for PostgreSQL.
Jan
|
| |
|
|
|
|
|
|
|
|
| |
of option switches for backend, fix handling of COPY from data files so
that we won't have the newline-after-\. issue back again, add back some
comments and printouts lost from the shell script, etc. Still needs work
for error handling; in particular the shell version worked much more
nicely for the case of a postgres executable that fails on invocation.
|
|
|
|
| |
add a header comment/copyright notice.
|
| |
|
| |
|
| |
|
|
|
|
| |
Andrew Dunstan
|
|
|
|
|
|
|
|
|
| |
I added a couple more Assertions while tracking down the exact
cause of the former bug.
All 93 regression tests pass now.
Jan
|
|
|
|
| |
Jan
|
| |
|
|
|
|
| |
come out before the action is done.
|
| |
|
|
|
|
|
|
| |
algorithm adopted for PostgreSQL.
Jan
|
|
|
|
|
| |
my fault. Adding it fixes bogus message display when reading a block
comment at the end of a script file.
|
|
|
|
|
|
|
|
|
|
| |
pghackers proposal of 8-Nov. All the existing cross-type comparison
operators (int2/int4/int8 and float4/float8) have appropriate support.
The original proposal of storing the right-hand-side datatype as part of
the primary key for pg_amop and pg_amproc got modified a bit in the event;
it is easier to store zero as the 'default' case and only store a nonzero
when the operator is actually cross-type. Along the way, remove the
long-since-defunct bigbox_ops operator class.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- 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.
|
| |
|
| |
|