- 08 8月, 2006 8 次提交
-
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
Lots of small changes in regression test suite
-
由 Bruce Momjian 提交于
< * Allow protocol-level BIND parameter values to be logged < < http://archives.postgresql.org/pgsql-hackers/2006-02/msg00165.php > * -Allow protocol-level BIND parameter values to be logged, if text mode
-
由 Bruce Momjian 提交于
o print user name for all o print portal name if defined for all o print query for all o reduce log_statement header to single keyword o print bind parameters as DETAIL if text mode
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
archiver to behave per original coder's expectation on these machines. We already know this everywhere else AFAICT.
-
由 Teodor Sigaev 提交于
what was a reason to corrupt index. Thank to Mario Weilguni <mweilguni@sime.com> to discover a bug.
-
由 Tom Lane 提交于
operation every so often. This improves the usefulness of PITR log shipping for hot standby: formerly, if the standby server crashed, it was necessary to restart it from the last base backup and replay all the WAL since then. Now it will only need to reread about the same amount of WAL as the master server would. The behavior might also come in handy during a long PITR replay sequence. Simon Riggs, with some editorialization by Tom Lane.
-
- 07 8月, 2006 1 次提交
-
-
由 Michael Meskes 提交于
Fixed and cleaned up some regression tests. Also added a new one.
-
- 06 8月, 2006 5 次提交
-
-
由 Tom Lane 提交于
without indexes) but not to display temp tables. It's a bit hard to credit that sanity_check could get through a database-wide VACUUM while the preceding create_index test is still trying to clean up its temp tables ... but I see no other explanation for the current failure report from buildfarm member sponge.
-
由 Tom Lane 提交于
to happen automatically during pg_stop_backup(). Add some functions for interrogating the current xlog insertion point and for easily extracting WAL filenames from the hex WAL locations displayed by pg_stop_backup and friends. Simon Riggs with some editorialization by Tom Lane.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
list, when some of the child rels have been excluded by constraint exclusion. This doesn't save a huge amount of time but it'll save some, and it makes the EXPLAIN output look saner. We already did the equivalent thing in set_append_rel_pathlist(), but not here.
-
由 Michael Meskes 提交于
-
- 05 8月, 2006 10 次提交
-
-
由 Neil Conway 提交于
Patch from Michael Fuhr.
-
由 Tom Lane 提交于
contradictory WHERE-clauses applied to a relation. This makes the GUC variable constraint_exclusion rather inappropriately named, but I've refrained for the moment from renaming it. Per example from Martin Lesser.
-
由 Tom Lane 提交于
This doesn't matter too much for ordinary NOTs, since prepqual.c does its best to get rid of those, but it helps with IS NOT TRUE clauses which the rule rewriter likes to insert. Per example from Martin Lesser.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
that's shorter-lived than the expression state being evaluated in it really doesn't work :-( --- we end up with fn_extra caches getting deleted while still in use. Rather than abandon the notion of caching expression state across domain_in calls altogether, I chose to make domain_in a bit cozier with ExprContext. All we really need for evaluating variable-free expressions is an ExprContext, not an EState, so I invented the notion of a "standalone" ExprContext. domain_in can prevent resource leakages by doing a ReScanExprContext on this rather than having to free it entirely; so we can make the ExprContext have the same lifespan (and particularly the same per_query memory context) as the expression state structs.
-
由 Bruce Momjian 提交于
Hiroshi Saito
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
these options were used before -n/-t.
-
由 Tom Lane 提交于
warnings on some compilers.
-
由 Tom Lane 提交于
-
- 04 8月, 2006 11 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
not merely remove their contents. Else 'cvs update' complains.
-
由 Tom Lane 提交于
constant input. Seems worth doing because rule rewriter inserts IS NOT TRUE tests into WHERE clauses.
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
supresses compiler warning.
-
由 Tom Lane 提交于
Joachim Wieland
-
由 Tom Lane 提交于
the DROP pass rather than the ADD_CONSTR pass. On examining the code I think this was just an oversight rather than intentional, and it seems to satisfy the principle of least surprise better than the alternative solution that was discussed. Add an example to the ref page showing how to do ALTER TYPE and update the default in one command. Per gripe from Markus Bertheau that that wasn't possible.
-
由 Tom Lane 提交于
check). This isn't supported by pg_regress since the recent rewrite into C. While we could add char classes to pg_regress.c's code, it's not really needed at the moment: thanks to Andrew's patch to make pg_regress always accept the 'standard' comparison file, we can just drop the version check.
-
由 Tom Lane 提交于
rather than pointers to garbage, when calling AFTER STATEMENT triggers. Michael Fuhr
-
- 03 8月, 2006 5 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
'mod' and 'all', which is not the right order. SGML documentation order was correct. Report from Chander Ganesan.
-