| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Fixed and cleaned up some regression tests. Also added a new one.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Hiroshi Saito
|
| | |
|
| |
|
|
| |
these options were used before -n/-t.
|
| |
|
|
| |
warnings on some compilers.
|
| | |
|
| |
|
|
| |
not merely remove their contents. Else 'cvs update' complains.
|
| |
|
|
|
| |
constant input. Seems worth doing because rule rewriter inserts
IS NOT TRUE tests into WHERE clauses.
|
| | |
|
| |
|
|
| |
supresses compiler warning.
|
| |
|
|
| |
Joachim Wieland
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
rather than pointers to garbage, when calling AFTER STATEMENT triggers.
Michael Fuhr
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
'mod' and 'all', which is not the right order. SGML documentation order
was correct. Report from Chander Ganesan.
|
| |
|
|
|
|
| |
in recent -t/-n/-T/-N patch.
Small style cleanups.
|
| | |
|
| |
|
|
|
|
|
| |
temporary context that can be reset when advancing to the next sublist.
This is faster and more thorough at recovering space than the previous
method; moreover it will do the right thing if something in the sublist
tries to register an expression context callback.
|
| | |
|
| |
|
|
| |
transformInsertStmt: the target table is already in p_rtable at that point.
|
| | |
|
| |
|
|
|
| |
test to avoid expensive contain_vars_of_level() scan in the normal case
where we're not inside a rule.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Implemented EXEC SQL UNDEF.
Applied first version of the regression test patch by Joachim Wieland <joe@mcknight.de>.
|
| |
|
|
|
|
| |
(e.g. "INSERT ... VALUES (...), (...), ...") and elsewhere as allowed
by the spec. (e.g. similar to a FROM clause subselect). initdb required.
Joe Conway and Tom Lane.
|
| | |
|
| |
|
|
|
|
| |
lightweight locks.
Marc Munro
|
| |
|
|
|
|
| |
if table creation failed (the table already exists).
Martin Pitt
|
| |
|
|
|
|
|
| |
and -N options to exclude objects. Also support regular expressions for
option object names.
Greg Sabino Mullane
|
| | |
|
| |
|
|
| |
alternative test is specified but none succeeds.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
(table or index) before trying to open its relcache entry. This fixes
race conditions in which someone else commits a change to the relation's
catalog entries while we are in process of doing relcache load. Problems
of that ilk have been reported sporadically for years, but it was not
really practical to fix until recently --- for instance, the recent
addition of WAL-log support for in-place updates helped.
Along the way, remove pg_am.amconcurrent: all AMs are now expected to support
concurrent update.
|
| | |
|
| | |
|
