| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
GetFreeXLBuffer(): use Insert->LgwrResult instead of private LgwrResult
copy if it's more fresh (attempt to avoid acquiring info_lck/lgwr_lck).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as previously discussed.
It makes AIX and IRIX not use DST for dates before 1970.
The following expected files need to be removed from the regression tests,
they contain wrong results and are not needed any more.
src/test/regress/expected/horology-1947-PDT.out
src/test/regress/expected/tinterval-1947-PDT.out
src/test/regress/expected/abstime-1947-PDT.out
Zeugswetter Andreas
|
| |
|
| |
|
|
|
|
|
|
| |
definitions from K&R to ANSI C style, and fix broken assumption that
int and long are the same datatype. This repairs problems observed
on Alpha with regexps having between 32 and 63 states.
|
| |
|
|
|
|
|
|
|
|
|
| |
two transactions create the same table name concurrently, the one that
fails will complain about unique index pg_class_relname_index, rather than
about pg_type_typname_index which'll confuse most people. Free side
benefit: pg_class.reltype is correctly linked to the pg_type entry now.
It's been zero in all but the preloaded pg_class entries since who knows
when.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
When no suitable YACC is configured, supply useful informational messages
to users. (Same way flex has been handled for a while.)
|
|
|
|
|
|
|
|
|
|
|
| |
are now separate files "postgres.h" and "postgres_fe.h", which are meant
to be the primary include files for backend .c files and frontend .c files
respectively. By default, only include files meant for frontend use are
installed into the installation include directory. There is a new make
target 'make install-all-headers' that adds the whole content of the
src/include tree to the installed fileset, for use by people who want to
develop server-side code without keeping the complete source tree on hand.
Cleaned up a whole lot of crufty and inconsistent header inclusions.
|
| |
|
|
|
|
| |
decompress the existing fields unnecessarily.
|
|
|
|
|
| |
is clearly not maintainable, so dike it out in favor of calling the real
version in the backend's gram.y.
|
|
|
|
|
|
|
|
|
|
| |
any other client connections that may exist (which would only happen if
another client is currently in the authentication cycle). This avoids
wastage of open descriptors in a child. It might also explain peculiar
behaviors like not closing connections when expected, since the kernel
will probably not signal EOF as long as some other backend is randomly
holding open a reference to the connection, even if the client went away
long since ...
|
|
|
|
| |
runtime recovery OFF.
|
| |
|
| |
|
|
|
|
|
| |
honor library search path that we so carefully installed into the
executable ...
|
| |
|
|
|
|
| |
OffsetNumber == MaxOffsetNumber + 1 - there may be garbage there!
|
|
|
|
|
|
|
| |
elog(ERROR) not an Assert trap, since we've downgraded out-of-memory to
elog(ERROR) not a fatal error. Also, change the hard boundary from 256Mb
to 1Gb, just so that anyone who's actually got that much memory to spare
can play with TOAST objects approaching a gigabyte.
|
|
|
|
|
| |
future 'timestamp without time zone', which SQL claims is equivalent to
plain 'timestamp'.
|
|
|
|
| |
has UNION/INTERSECT/EXCEPT operations. Per bug report from Ferrier.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Need in one more function to handle "my bits moved..."
case. FixBTree is still FALSE.
|
| |
|
|
|
|
|
|
|
|
| |
allocated by plan nodes are not leaked at end of query. This doesn't
really matter for normal queries, but it sure does for queries invoked
repetitively inside SQL functions. Clean up some other grotty code
associated with tupdescs, and fix a few other memory leaks exposed by
tests with simple SQL functions.
|
| |
|
|
|
|
| |
table.
|
|
|
|
| |
triggers ... oops ... but the regress tests should have covered this ...
|
|
|
|
|
| |
not happen anyway, but let's try not to get completely confused if it does
(due to rewriter bugs or whatever).
|
|
|
|
|
|
|
|
| |
original table ('OLD' table) in its join tree if OLD is referenced by
either the rule action, the rule qual, or the original query qual that
will be added to the rule action. However, we only want one instance
of the original table to be included; so beware of the possibility that
the rule action already has a jointree entry for OLD.
|
|
|
|
|
|
| |
rather than coredumping (as prior 7.1 code did) or silently dropping the
condition (as 7.0 did). This is annoying but there doesn't seem to be
any good way to fix it, short of a major querytree restructuring.
|
|
|
|
| |
a NOTIFY.
|
|
|
|
|
|
| |
actually) to ensure that its file access time doesn't get old enough to
tempt a /tmp directory cleaner to remove it. Still another reason we
should never have put the sockets in /tmp in the first place ...
|
|
|
|
|
|
|
| |
truncating to integer. Remove regress test that checks whether
4567890123456789 can be converted to float without loss; since that's
52 bits, it's on the hairy edge of failing with IEEE float8s, and indeed
rint seems to give platform-dependent results for it.
|
|
|
|
|
| |
see if we shouldn't block whenever we insert ourselves anywhere before
the end of the queue, not only at the front.
|
|
|
|
|
|
|
| |
and new root page if old root one was splitted but new root page
wasn't created.
New code is protected by FixBTree bool flag setted to FALSE, so
nothing should be affected by this untested approach.
|
|
|
|
| |
rearranges wait queues.
|
|
|
|
| |
to pghackers on 18-Jan-01.
|
| |
|
| |
|
| |
|