| Age | Commit message (Collapse) | Author |
|---|
|
in the same transaction that created it.
|
|
Jan
|
|
198.68.123.0/27 the same when indexing them.
D'Arcy
|
|
all fields that should be set). Add a MoveToFront primitive to speed up
one of the hotspots in SearchSysCache.
|
|
in an index doesn't have a restriction selectivity estimator.
|
|
right circumstances it would leave old and new bucket headers pointing to
the same list of records.
|
|
cache access routines.
|
|
|
|
|
|
|
|
|
|
|
|
Jan
|
|
|
|
bigger the more space is used in an allocset. This reduces the malloc
overhead very substantially on queries that need lots of memory.
|
|
kernel's error description when file is not accessible).
|
|
from being accepted when they are passed from client connection request.
Get rid of a couple that no longer do anything (like -P).
|
|
|
|
|
|
pg_rules to rules regression test.
Jan
|
|
in Resdom and GroupClause so changing of resno's doesn't confuse
the grouping any more.
Jan
|
|
The
offending code
has been removed, the action is now always dependent :-)
I suggest the following patch, to finally make trigger regression happy
again:
<<refint1.patch>>
After that you can remove the following from TODO:
Remove ERROR: check_primary_key: even number of arguments should be
specified
Trigger regression test fails
Andreas
|
|
-d4 now prints compressed trees from nodeToString()
-d5 prints pretty trees via nodeDisplay()
new pg_options: pretty_plan, pretty_parse, pretty_rewritten
Jan
|
|
Jan
|
|
|
|
real affect now.
|
|
fopen(), instead of going through fd.c ... naughty naughty.
|
|
code, instead of not-very-bulletproof stuff they had before.
|
|
arrayfuncs.patch fixes a small bug in my previous patches for
arrays
array-regress.patch adds _bpchar and _varchar to regression tests
--
Massimo Dal Zotto
|
|
Original code used float8out(), but the resulting exponential notation
was not handled (e.g. '3E9' was decoded as '3').
|
|
gcc quite so unhappy.
|
|
been applied. The patches are in the .tar.gz attachment at the end:
varchar-array.patch this patch adds support for arrays of bpchar() and
varchar(), which where always missing from postgres.
These datatypes can be used to replace the _char4,
_char8, etc., which were dropped some time ago.
block-size.patch this patch fixes many errors in the parser and other
program which happen with very large query statements
(> 8K) when using a page size larger than 8192.
This patch is needed if you want to submit queries
larger than 8K. Postgres supports tuples up to 32K
but you can't insert them because you can't submit
queries larger than 8K. My patch fixes this problem.
The patch also replaces all the occurrences of `8192'
and `1<<13' in the sources with the proper constants
defined in include files. You should now never find
8192 hardwired in C code, just to make code clearer.
--
Massimo Dal Zotto
|
|
to save a little bit of backend startup time. This way, the first
backend started after a VACUUM will rebuild the init file with up-to-date
statistics for the critical system indexes.
|
|
an identifier :-(. Sloppy transmission of a patch, likely.
|
|
Jan
|
|
|
|
different from database's ...
|
|
it failed to cover the case where high bits of char are 100 or 101.
Not sure if fix is right, but it agrees with pg_utf_mblen ... and it
doesn't lock up ...
|
|
|
|
can be generated in a buffer and then sent to the frontend in a single
libpq call. This solves problems with NOTICE and ERROR messages generated
in the middle of a data message or COPY OUT operation.
|
|
instead of doing a kill(self, SIGQUIT) and expecting the signal handler
to do it. Also, clean up inconsistent definitions of the sigjmp buffer
in the several files that already referenced it.
|
|
and related files. Also remove float.c's gratuitous redeclaration of
isinf() ... looks like there are more decls in there that ought to be
in config.h, but I'll leave well enough alone for now ...
|
|
MyProcPid global variable is set to 0 when postgres starts as a command
(not as a backend daemon). This leads issuing SIGQUIT to the process group,
not the process itself. As a result, parent sh gets core dumped in the
Wisconsin benchmark test.
|
|
rather than reusing the input storage.
Also made the same fix to int8smaller(), though there wasn't a symptom,
and went through and verified that other pass-by-reference data types
do the same thing. Not an issue for the by-value types.
|
|
time zone.
Previously, localtime() rotated a date with a day of month field which
exceeded the actual range into the next months, masking the fact that
a bad date had been specified.
Regression tests pass.
|
|
mis-copied "NULL", which happens to have the same binary value.
Previously, gcc gave non-fatal warnings.
|
|
|
|
making prosrc instead of proname be the link to the actual internal function.
|
|
Use memcpy() rather than StrNCpy() which had forced a string termination
character at the end.
|
|
(may be used while vacuuming unique btree-s).
|
