- 03 2月, 2008 1 次提交
-
-
由 Tom Lane 提交于
erroring out of a wait. We can use a PG_TRY block for this, but add a comment explaining why it'd be a bad idea to use it for any other state cleanup. Back-patch to 8.2. Prior releases had the same issue, but only with respect to the process title, which is likely to get reset almost immediately anyway after the transaction aborts, so it seems not worth changing them. In 8.2 and HEAD, the pg_stat_activity "waiting" flag could remain set incorrectly for a long time. Per report from Gurjeet Singh.
-
- 01 2月, 2008 14 次提交
-
-
由 Marc G. Fournier 提交于
configure tag'd 8.3.0 and built witih autoconf 2.59
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Improve deadlock detection when deleting items from shared buffers > * Improve deadlock detection when a page cleaning lock conflicts > with a shared buffer that is pinned
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
<!-- If this URL chnages replace it with a URL to www.archive.org. -->
-
由 Bruce Momjian 提交于
name of the needed symlink file.
-
由 Tom Lane 提交于
Update expected release date.
-
由 Tom Lane 提交于
buildfarm plus a narrative description of the CPU types and operating systems on which Postgres is likely to work. Now that we've almost completely decoupled CPU and OS considerations, the former tabular style isn't all that enlightening anyway. Perhaps more importantly, no one seems particularly interested in maintaining the table by hand when we have the buildfarm.
-
由 Tom Lane 提交于
work with the PQExpBuffer code instead of fighting it. This avoids an unnecessary limit on message length and fixes the latent bug that errorMessage.len wasn't getting set.
-
由 Tom Lane 提交于
prevent anti-wraparound vacuuming, and to caution against setting unreasonably small values of freeze_max_age. Also put in a notice that this catalog is likely to disappear entirely in some future release. Per discussion of bug #3898 from Steven Flatt.
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
spoofing when the socket file has been moved.
-
由 Andrew Dunstan 提交于
-
- 31 1月, 2008 5 次提交
-
-
由 Bruce Momjian 提交于
> * Improve deadlock detection when deleting items from shared buffers > > http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php > http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php
-
由 Magnus Hagander 提交于
Should fix a problem where two clusters are running under two different service accounts and get colliding names, causing only the first cluster to contain the pgident event description. Per report from Stephen Denne.
-
由 Andrew Dunstan 提交于
Keep the intermediate symbol file rather then blowing it away, for easier debugging.
-
由 Tom Lane 提交于
operations when the current transaction has any open references to the target relation or index (implying it has an active query using the relation). The need for this was previously recognized in connection with ALTER TABLE, but anything that summarily eliminates tuples or moves them around would confuse an active scan. While this patch does not in itself fix bug #3883 (the deadlock would happen before the new check fires), it will discourage people from attempting the sequence of operations that creates a deadlock risk, so it's at least a partial response to that problem. In passing, add a previously-missing check to REINDEX to prevent trying to reindex another backend's temp table. This isn't a security problem since only a superuser would get past the schema permission checks, but if we are testing for this in other utility commands then surely REINDEX should too.
-
由 Tom Lane 提交于
synchronized-scanning behavior, and make pg_dump disable sync scans so that it will reliably preserve row ordering. Per recent discussions.
-
- 30 1月, 2008 7 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
soon. I suspect this explains bug #3902, though I'm still not able to reproduce that.
-
由 Bruce Momjian 提交于
< * Add anonymous transactions > * Add autonomous transactions
-
由 Bruce Momjian 提交于
> * Add anonymous transactions > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php >
-
由 Bruce Momjian 提交于
< o Allow the PITR process to be debugged and data examined
-
- 29 1月, 2008 4 次提交
-
-
由 Peter Eisentraut 提交于
from Gevik Babakhani
-
由 Tom Lane 提交于
the patch for those features put its cleanup code into freePGconn() which is really the wrong place. Remove redundant code from freePGconn() and add comments in hopes of preventing similar mistakes in future. Noticed while trying (futilely) to reproduce bug #3902.
-
由 Tom Lane 提交于
are known to write on the socket sometimes and thus we are vulnerable to being killed by the signal if the server happens to go away unexpectedly. Noticed while trying (futilely) to reproduce bug #3902. This bug has been there all along, but since the situation is usually only of interest to developers, I chose not to back-patch the changes.
-
由 Bruce Momjian 提交于
-
- 28 1月, 2008 1 次提交
-
-
由 Tom Lane 提交于
in particular correct the obsolete claim that it can't be changed once any plans have been cached.
-
- 27 1月, 2008 1 次提交
-
-
由 Tom Lane 提交于
whether to execute an immediate interrupt, rather than testing whether LockWaitCancel() cancelled a lock wait. The old way misclassified the case where we were blocked in ProcWaitForSignal(), and arguably would misclassify any other future additions of new ImmediateInterruptOK states too. This allows reverting the old kluge that gave LockWaitCancel() a return value, since no callers care anymore. Improve comments in the various implementations of PGSemaphoreLock() to explain that on some platforms, the assumption that semop() exits after a signal is wrong, and so we must ensure that the signal handler itself throws elog if we want cancel or die interrupts to be effective. Per testing related to bug #3883, though this patch doesn't solve those problems fully. Perhaps this change should be back-patched, but since pre-8.3 branches aren't really relying on autovacuum to respond to SIGINT, it doesn't seem critical for them.
-
- 26 1月, 2008 1 次提交
-
-
由 Tom Lane 提交于
a double-pfree crash and another that effectively disabled size-based rotation for CSV logs. Also suppress a memory leak and make some trivial cosmetic improvements. Per bug #3901 from Chris Hoover and additional code-reading.
-
- 25 1月, 2008 2 次提交
-
-
由 Andrew Dunstan 提交于
of escaping bytea return value. Both cases did not handle backslash values properly.
-
由 Tom Lane 提交于
ri_FetchConstraintInfo, to avoid a query-duration memory leak when that routine is called by RI_FKey_keyequal_upd_fk (which isn't executed in a short-lived context). This problem was latent when the routine was added in February, but it didn't become serious until the varvarlena patch made it quite likely that the fields being examined would be "toasted" (ie, have short headers). Per report from Stephen Denne.
-
- 24 1月, 2008 4 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
TimestampTzPlusMilliseconds. An integer argument of more than INT_MAX/1000 milliseconds (ie, about 35 minutes) would provoke a wrong result, resulting in incorrect enforcement of statement_timestamp values larger than that. Bug was introduced in my rewrite of 2006-06-20, which fixed some other overflow risks, but missed this one :-( Per report from Elein.
-
由 Tom Lane 提交于
Per discussion of bug #3877. Simon Riggs, some fixes by moi.
-
由 Tom Lane 提交于
zero with a CASE expression. Per gripe from Russell Smith.
-