| Age | Commit message (Collapse) | Author |
|---|
|
left input's sorting, because null rows may be inserted at various points.
Per report from Ferenc Lutischá¸n.
|
|
Lowercase some uppercase tags so tools is more reliable at finding
problems.
|
|
tablespace instead of the index's own), except when the index was created
as a constraint. Report and fix by Tanida Yutaka.
|
|
pre-7.3 pg_dump archive files: namespace isn't there, and in some cases
te->tag may already be quotified. Per report from Alan Pevec and
followup testing.
|
|
|
|
pass if "default_with_oids" is set to false. I took the approach of
explicitly adding WITH OIDS to the CREATE TABLEs where necessary, rather
than tweaking the default_with_oids GUC var.
|
|
|
|
expression types.
|
|
|
|
(1) Keep a pin on the scan's current buffer and mark buffer. This
avoids the need to do a ReadBuffer() for each tuple produced by the
scan. Since ReadBuffer() is expensive, this is a significant win.
(2) Convert a ReleaseBuffer(); ReadBuffer() pair into
ReleaseAndReadBuffer(). Surely not a huge win, but it saves a lock
acquire/release...
(3) Remove a bunch of duplicated code in rtget.c; make rtnext() handle
both the "initial result" and "subsequent result" cases.
(4) Add support for index tuple killing
(5) Remove rtscancache(): it is dead code, for the same reason that
gistscancache() is dead code (an index scan ought not be invoked with
NoMovementScanDirection).
The end result is about a 10% improvement in rtree index scan perf,
according to contrib/rtree_gist/bench.
|
|
good style and to satisfy sparse. From Alvaro Herrera.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
an untyped literal in the CASE's test expression. This adds test
coverage for a bug that was fixed by Tom on January 12.
|
|
|
|
|
|
|
|
the right place in the docs, and gettext()ify it.
|
|
per Andrew Dunstan. Also, don't override the user's value of PGHOST
in the 'make installcheck' case. I think the latter was an ill-considered
workaround for the Windows code back when libpq didn't properly default
to localhost on Unix-socket-less platforms.
|
|
failure in SelectConfigFiles(). Cosmetic issue, but ...
|
|
|
|
to get these strings translated, but we may as well have them be
translatable as not.
|
|
as a statement trigger :-(. Per report from Sokolov Yura.
|
|
|
|
|
|
MemoryContextAllocZero back to MemoryContextAlloc, same as it was in 7.4.
The zeroing is unnecessary since all the meaningful fields are filled in
just below. I had made it do that out of neatnik-ism, but some testing
with an example provided by Pavel Stehule showed that the zeroing was
accounting for about 5% of the runtime in a compute-intensive plpgsql
function. That seems a bit high of a price for neatnik-ism...
|
|
|
|
|
|
tutorial to be used without necessarily having a configured source tree.
|
|
got it wrong when the JOIN was in an outer query level. Per example from
Laurie Burrow. Also fix same issue in markTargetListOrigin. I think the
latter is only a latent bug since we currently don't apply markTargetListOrigin
except at the outer level ... but should do it right anyway.
|
|
of an sprintf() as a source string. Demonstrably does not work with
recent gcc and/or glibc on some platforms.
|
|
version of Kerberos. Per report from Reinhard Max.
|
|
CASE 'a' WHEN 'a' THEN 1 ELSE 2 END. This worked in 7.4 and before
but had been broken due to premature freezing of the type of the test
expression. Per gripe from GÄbor SzÃcs.
|
|
telling when it has been exceeded. Per trouble report from
Jean-GÅrard Pailloncy.
|
|
few 'listen_addresses' as possible --- on most systems, none at all,
just the Unix socket. This avoids spurious check failures due to bogus
DNS setups, and is probably a good idea from a security standpoint anyway.
Per trouble report from Jean-GÅrard Pailloncy.
|
|
GERMAN datestyles. Ancient bug reported by Terry Lee Tucker.
|
|
Per report from Robert Koepferl.
|
|
returned by Perl. Per report from Nicolas Addington.
|
|
|
|
pkey/unique constraint indexes) and schemas. Per report from
Michael Fuhr.
|
|
so that we can get the size of a shared inval message back down to what it
was in 7.4 (and simplify the logic too). Phase 2 of fixing the
'SMgrRelation hashtable corrupted' problem.
|
|
is the minimum required fix. I want to look next at taking advantage of
it by simplifying the message semantics in the shared inval message queue,
but that part can be held over for 8.1 if it turns out too ugly.
|
|
|
|
|
