Age | Commit message (Collapse) | Author |
|
|
|
|
|
of minus zero. Per Andrew Dunstan.
|
|
Fabien COELHO
|
|
Reini Urban
|
|
Just paranoia ...
|
|
|
|
|
|
|
|
Rather than using ReadBuffer() to increment the reference count on an
already-pinned buffer, we should use IncrBufferRefCount() as it is
faster and does not require acquiring the BufMgrLock.
|
|
been defined. Patch from Gavin Sherry, editorializing by Neil Conway.
|
|
even uglier than it was already :-(. Also, on Windows only, use temporary
shared memory segments instead of ordinary files to pass over critical
variable values from postmaster to child processes. Magnus Hagander
|
|
more than 65K columns, or when the created table has more than 65K columns
due to adding inherited columns from parent relations. Fix a similar
crash when processing SELECT queries with more than 65K target list
entries. In all three cases we would eventually detect the error and
elog, but the check was being made too late.
|
|
|
|
patch, but allow srand and disallow sprintf as per subsequent discussion.
|
|
Andrew Dunstan
|
|
Magnus Hagander
|
|
We don't really want to start a new SPI connection, just keep using the old
one; otherwise we have memory management problems as illustrated by
John Kennedy's bug report of today. This requires a bit of a hack to
ensure the SPI stack state is properly restored, but then again what we
were doing before was a hack too, strictly speaking. Add a regression
test to cover this case.
|
|
|
|
|
|
plain SUSET instead. Also delay processing of options received in
client connection request until after we know if the user is a superuser,
so that SUSET values can be set that way by legitimate superusers.
Per recent discussion.
|
|
buffer is valid, as ReadBuffer() will elog on error. Most of the call
sites of ReadBuffer() got this right, but this patch fixes those call
sites that did not.
|
|
lacking pqsignal which is now required. This was found and fixed for
VC++ by Shachar Shemesh, I simply duplicated the fix for the Borland
makefile (untested, as I don't have that compiler).
Dave Page
|
|
|
|
> pg specific, like "PostgreSQL.1". I have not done this since a new compile
> would not detect a running old beta. But now would be the time (or never).
Zeugswetter Andreas
|
|
since this path will lead to postmaster exit anyway...)
|
|
|
|
! printf(_(" -d, --dbname=NAME connect to database name\n"));
! printf(_(" -C, --create create the target database\n"));
|
|
a global variable to control building indexes.
|
|
|
|
selectivity estimates, per recent discussion.
|
|
shared memory segment ID. If we can't access the existing shmem segment,
it must not be relevant to our data directory. If we can access it,
then attach to it and check for an actual match to the data directory.
This should avoid some cases of failure-to-restart-after-boot without
introducing any significant risk of failing to detect a still-running
old backend.
|
|
malloc() doesn't set errno, so most uses were buggy anyway.
|
|
|
|
|
|
|
|
|
|
|
|
from Alvaro Herrera.
|
|
estimates when combining the estimates for a range query. As pointed out
by Miquel van Smoorenburg, the existing check for an impossible combined
result would quite possibly fail to detect one default and one non-default
input. It seems better to use the default range query estimate in such
cases. To do so, add a check for an estimate of exactly DEFAULT_INEQ_SEL.
This is a bit ugly because it introduces additional coupling between
clauselist_selectivity and scalarltsel/scalargtsel, but it's not like
there wasn't plenty already...
|
|
|
|
than erroring out. This is the Unix behavior.
|
|
working as intended --- for some reason, FROM a.b.c was getting
parsed as if it were a function name and not a qualified name.
I think there must be a bug in bison, because it should have
complained that the grammar was ambiguous. Anyway, fix it along
the same lines previously used for func_name vs columnref, and get
rid of the right-recursion in attrs that seems to have confused
bison.
|
|
shifting left by full word width gives zero. Per bug report from
Tyson Thomson.
|
|
|
|
|
|
|
|
preserve double leading slashes on Win32.
e.g. ////a////b => /a/b
|
|
actual executable location. This allows people to continue to use
setups where, eg, postmaster is symlinked from a convenient place.
Per gripe from Josh Berkus.
|
|
won't have trivial differences in their common prefix.
|