- 16 1月, 2008 4 次提交
-
-
由 Tom Lane 提交于
introduced in rewrite to make CLUSTER MVCC-safe.
-
由 Tom Lane 提交于
in whichever context happens to be current during a call of an xml.c function, use a dedicated context that will not go away until we explicitly delete it (which we do at transaction end or subtransaction abort). This makes recovery after an error much simpler --- we don't have to individually delete the data structures created by libxml. Also, we need to initialize and cleanup libxml only once per transaction (if there's no error) instead of once per function call, so it should be a bit faster. We'll need to keep an eye out for intra-transaction memory leaks, though. Alvaro and Tom.
-
由 Tom Lane 提交于
-
由 Teodor Sigaev 提交于
-
- 15 1月, 2008 7 次提交
-
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
> > * Add the ability to automatically create materialized views > > Right now materialized views require the user to create triggers on the > main table to keep the summary table current. SQL syntax should be able > to manager the triggers and summary table automatically. A more > sophisticated implementation would automatically retrieve from the > summary table when the main table is referenced, if possible. >
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
This is to avoid uselessly requiring superuser permissions to restore the dump without errors. Pretty grotty, but no better alternative seems available, at least not in the near term.
-
由 Tom Lane 提交于
during transaction abort, per my note from a couple days ago.
-
由 Tom Lane 提交于
we need to be able to swallow NOTICE messages, and potentially also ParameterStatus messages (although the latter would be a bit weird), without exiting COPY OUT state. Fix it, and adjust the protocol documentation to emphasize the need for this. Per off-list report from Alexander Galler.
-
- 14 1月, 2008 7 次提交
-
-
由 Alvaro Herrera 提交于
distinguished from user-invoked commands. Per suggestion from Tom Lane.
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
higher than zero. Same problem as just detected in CREATE INDEX CONCURRENTLY.
-
由 Tom Lane 提交于
Noted while looking for heapscans that might need to start from block zero.
-
由 Tom Lane 提交于
its second pass over the table. It has to start at block zero, else the "merge join" logic for detecting which TIDs are already in the index doesn't work. Hence, extend heapam.c's API so that callers can enable or disable syncscan. (I put in an option to disable buffer access strategy, too, just in case somebody needs it.) Per report from Hannes Dorbath.
-
由 Tom Lane 提交于
'english'.
-
由 Tom Lane 提交于
command IDs.
-
- 13 1月, 2008 3 次提交
-
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
! Duplicate positions for the same lexeme are discarded.
-
由 Tom Lane 提交于
Therefore we must xmlCleanupParser(), or we risk leaving behind dangling pointers to whatever memory context is current when xml_init() is called. This seems to fix bug #3860, though we might still want the more invasive solution being worked on by Alvaro.
-
- 12 1月, 2008 6 次提交
-
-
由 Neil Conway 提交于
SPI_prepare() and SPI_cursor_open(), to silence a Coverity warning.
-
由 Neil Conway 提交于
anyway, it is faster to memcpy() than to strcpy().
-
由 Tom Lane 提交于
constraint yields TRUE for every row of its table, only that it does not yield FALSE (a NULL result isn't disallowed). This breaks a couple of implications that would be true in two-valued logic. I had put in one such mistake in an 8.2.5 patch: foo IS NULL doesn't refute a strict operator on foo. But there was another in the original 8.2 release: NOT foo doesn't refute an expression whose truth would imply the truth of foo. Per report from Rajesh Kumar Mallah. To preserve the ability to do constraint exclusion with one partition holding NULL values, extend relation_excluded_by_constraints() to check for attnotnull flags, and add col IS NOT NULL expressions to the set of constraints we hope to refute.
-
由 Tom Lane 提交于
checking of argument compatibility right; although the problem is only exposed with multiple-input aggregates in which some arguments are polymorphic and some are not. Per bug #3852 from Sokolov Yura.
-
由 Tom Lane 提交于
for unhandled clause types ought to be 0.5, not 1.0. I fear I introduced this silliness due to misreading the intent of the very-poorly-structured code that was there when we inherited the file from Berkeley. The lack of sanity in this behavior was exposed by an example from Sim Zacks. (Arguably this is a bug fix and should be back-patched, but I'm a bit hesitant to introduce a possible planner behavior change in the back branches; it might detune queries that worked acceptably in the past.) While at it, make estimation for DistinctExpr do something marginally realistic, rather than just defaulting.
-
由 Bruce Momjian 提交于
> * Add ability to trigger on TRUNCATE > > http://archives.postgresql.org/pgsql-sql/2008-01/msg00050.php
-
- 11 1月, 2008 4 次提交
-
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
clauseless joins of relations that have unexploited join clauses. Rather than looking at every other base relation in the query, the correct thing is to examine the other relations in the "initial_rels" list of the current make_rel_from_joinlist() invocation, because those are what we actually have the ability to join against. This might be a subset of the whole query in cases where join_collapse_limit or from_collapse_limit or full joins have prevented merging the whole query into a single join problem. This is a bit untidy because we have to pass those rels down through a new PlannerInfo field, but it's necessary. Per bug #3865 from Oleg Kharin.
-
由 Tom Lane 提交于
finish archiving everything (when there's no error), and to eliminate various hazards as best we can. This fixes a previous 8.3 patch that caused the postmaster to kill and then restart the archiver during shutdown (!?). The new behavior is that the archiver is allowed to run unmolested until the bgwriter has exited; then it is sent SIGUSR2 to tell it to do a final archiving cycle and quit. We only SIGQUIT the archiver if we want a panic stop; this is important since SIGQUIT will also be sent to any active archive_command. The postmaster also now doesn't SIGQUIT the stats collector until the bgwriter is done, since the bgwriter can send stats messages in 8.3. The postmaster will not exit until both the archiver and stats collector are gone; this provides some defense (not too bulletproof) against conflicting archiver or stats collector processes being started by a new postmaster instance. We continue the prior practice that the archiver will check for postmaster death immediately before issuing any archive_command; that gives some additional protection against conflicting archivers. Also, modify the archiver process to notice SIGTERM and refuse to issue any more archive commands if it gets it. The postmaster doesn't ever send it SIGTERM; we assume that any such signal came from init and is a notice of impending whole-system shutdown. In this situation it seems imprudent to try to start new archive commands --- if they aren't extremely quick they're likely to get SIGKILL'd by init. All per discussion.
-
由 Magnus Hagander 提交于
Hiroshi Saito
-
- 10 1月, 2008 4 次提交
-
-
由 Bruce Momjian 提交于
postgresql.conf comment to match.
-
由 Tom Lane 提交于
pg_convert_to. Per bug #3866 from Andrew Gilligan.
-
由 Tom Lane 提交于
VACUUM that is blocked waiting to get lock on the table being indexed. Per report and fix suggestion from Greg Stark.
-
由 Tom Lane 提交于
of poorer planning in 8.3 than 8.2: 1. After pushing a constant across an outer join --- ie, given "a LEFT JOIN b ON (a.x = b.y) WHERE a.x = 42", we can deduce that b.y is sort of equal to 42, in the sense that we needn't fetch any b rows where it isn't 42 --- loop to see if any additional deductions can be made. Previous releases did that by recursing, but I had mistakenly thought that this was no longer necessary given the EquivalenceClass machinery. 2. Allow pushing constants across outer join conditions even if the condition is outerjoin_delayed due to a lower outer join. This is safe as long as the condition is strict and we re-test it at the upper join. 3. Keep the outer-join clause even if we successfully push a constant across it. This is *necessary* in the outerjoin_delayed case, but even in the simple case, it seems better to do this to ensure that the join search order heuristics will consider the join as reasonable to make. Mark such a clause as having selectivity 1.0, though, since it's not going to eliminate very many rows after application of the constant condition. 4. Tweak have_relevant_eclass_joinclause to report that two relations are joinable when they have vars that are equated to the same constant. We won't actually generate any joinclause from such an EquivalenceClass, but again it seems that in such a case it's a good idea to consider the join as worth costing out. 5. Fix a bug in select_mergejoin_clauses that was exposed by these changes: we have to reject candidate mergejoin clauses if either side was equated to a constant, because we can't construct a canonical pathkey list for such a clause. This is an implementation restriction that might be worth fixing someday, but it doesn't seem critical to get it done for 8.3.
-
- 09 1月, 2008 5 次提交
-
-
由 Magnus Hagander 提交于
builds of libpq in both 32 and 64-bit. Per gripe from Hiroshi Saito.
-
由 Neil Conway 提交于
and grpOperators fields were not emitted by _outAgg().
-
由 Alvaro Herrera 提交于
-
由 Bruce Momjian 提交于
are moved to SGML.
-
由 Tom Lane 提交于
Also a couple of minor tweaks to try to future-proof the code a bit better against future locktag additions.
-