| Age | Commit message (Collapse) | Author |
|---|
|
Probably the right fix is to remove 'current' special value entirely,
but I don't want to see regression test failures until that happens.
|
|
actually work. It had been throwing an Assert as of my recent changes
to bufmgr.c, but was not really right even before that AFAICT.
|
|
immediately, we will fork a child even if the database state does not
permit connections to be accepted (eg, we are in recovery mode).
The child process will correctly reject the connection and exit as
soon as it's finished collecting the connection request message.
However, this means that reaper() must be prepared to see child
process exit signals even while it's waiting for startup or shutdown
process to finish. As was, a connection request arriving during a
database recovery or shutdown would cause postmaster abort.
|
|
characteristics) to be set through GUC.
|
|
|
|
|
|
have localized strings.) Also, modernize the system catalog queries where
appropriate, e.g., with outer joins.
|
|
Add 'do { ... } while (0)' decoration to eliminate compiler warnings.
|
|
stub) into the rest of the system. Adopt a cleaner approach to preventing
deadlock in concurrent heap_updates: allow RelationGetBufferForTuple to
select any page of the rel, and put the onus on it to lock both buffers
in a consistent order. Remove no-longer-needed isExtend hack from
API of ReleaseAndReadBuffer.
|
|
have any newly-dead tuples on them. This is a longstanding deficiency
that prevents VACUUM from compacting a file as much as one would expect.
Change requires fixing repair_frag to not assume that fraged_pages is
a subset of vacuum_pages.
Also make some further cleanups of places that assumed page numbers fit
in int and tuple counts fit in uint32.
|
|
Barry Lind
|
|
after writing/unpinning it. An actual failure is unlikely, unless the
system is tremendously short of buffers ... but a bug is a bug.
|
|
for speed.
Jan
|
|
|
|
|
|
do anything yet, but it has the necessary connections to initialization
and so forth. Make some gestures towards allowing number of blocks in
a relation to be BlockNumber, ie, unsigned int, rather than signed int.
(I doubt I got all the places that are sloppy about it, yet.) On the
way, replace the hardwired NLOCKS_PER_XACT fudge factor with a GUC
variable.
|
|
message clean up.
|
|
confusing definitions in it.
|
|
Now the version is 7.01.0006.
|
|
directly, rather than through SetConfigOption().
|
|
directly, rather than through SetConfigOption().
|
|
IS TRUE, etc, with some degree of verisimilitude. Split out
selectivity support functions from builtins.h into a new header
file selfuncs.h, so as to reduce the number of header files builtins.h
must depend on. Fix a few missing inclusions exposed thereby.
From Joe Conway, with some kibitzing from Tom Lane.
|
|
|
|
Here is a patch which inspired by Michael Stephens that should work
Dave Cramer
|
|
|
|
|
|
message in that case.
|
|
> > secure_ctx changes too. it will be PGC_BACKEND after '-p'.
>
> Oh, okay, I missed that part. Could we see the total state of the
> patch --- ie, a diff against current CVS, not a bunch of deltas?
> I've gotten confused about what's in and what's out.
Ok, here it is. Cleared the ctx comment too - after -p
it will be PGC_BACKEND in any case.
Marko Kreen
|
|
sequence.
|
|
Alex Pilosov
|
|
Jan
|
|
it's hard to keep such massive changes in sync with the tree
so I need to get it in and work from there now).
Jan
|
|
oid values.
|
|
other than tablename_pkey.
|
|
return without waiting if we can't get the lock immediately).
Not used yet, but will be needed for concurrent VACUUM.
|
|
|
|
|
|
|
|
ordering of startup operations in one or two places.
|
|
(see http://mail.gnu.org/pipermail/libtool/2000-July/001824.html). But
apparently it should still be present with -Bsymbolic.
|
|
from Johnny C. Lam <lamj@stat.cmu.edu> via D'Arcy
|
|
to be missing in some header files (on OpenBSD 2.8?).
|
|
|
|
|
|
a new postmaster child process. This should eliminate problems with
authentication blocking (e.g., ident, SSL init) and also reduce problems
with the accept queue filling up under heavy load.
The option to send elog output to a different file per backend (postgres -o)
has been disabled for now because the initialization would have to happen
in a different order and it's not clear we want to keep this anyway.
|
|
|
|
make sure that we are using the right #defines in pgmodule.c but the
OIDs are never actually expected to change.
|
|
by multiple SQLError calls.
|
|
broken, and its impossible to make a shared library when compiling with
both CCDLFLAGS and LDDLFAGS, you have to pick one or the other.
Alex Pilosov
|
|
|
