- 30 1月, 2008 2 次提交
-
-
由 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.
-
- 23 1月, 2008 4 次提交
-
-
由 Alvaro Herrera 提交于
-
由 Tom Lane 提交于
no-longer-maintained PgAccess. Per Erik Rijkers.
-
由 Andrew Dunstan 提交于
* The temporary enabling of the caller opcode here is to work around a * bug in perl 5.10, which unkindly changed the way its Safe.pm works, without * notice. It is quite safe, as caller is informational only, and in any case * we only enable it while we load the 'strict' module.
-
由 Andrew Dunstan 提交于
-
- 21 1月, 2008 5 次提交
-
-
由 Peter Eisentraut 提交于
wrong because of mismatched byte ordering.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
regis. Correct the latter's oversight that a bracket-expression needs to be terminated. Reduce the ereports to elogs, since they are now not expected to ever be hit (thus addressing Alvaro's original complaint). In passing, const-ify the string argument to RS_compile.
-
由 Tom Lane 提交于
to format properly for the actually needed column width, instead of having a hard-wired assumption about the longest command name length. Also make it respond to the current screen width. In passing, const-ify the constant table.
-
由 Alvaro Herrera 提交于
-
- 20 1月, 2008 1 次提交
-
-
由 Tom Lane 提交于
On other platforms it's better to let the Makefile handle it, but we want the regression tests to be invokable without make on Windows. A batch file would be a better solution, but no time for that before 8.3. Per my discovery that this breaks testing under SELinux, and subsequent discussion.
-
- 18 1月, 2008 6 次提交
-
-
由 Marc G. Fournier 提交于
must commit after autoconf ... and yes, I used the right autoconf
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
main code path for enlarging libpq's input buffer in one swoop when needing to read a long data message. Without this, the code will double the buffer size, read more data, notice it still hasn't got the whole message, and repeat till it finally has a large enough buffer. Which wastes a lot of data-moving effort and also memory (since malloc probably can't do anything very useful with the freed-up smaller buffers). Not sure why this wasn't there already; certainly the COPY data path is a place where we're quite likely to see long data messages. I'm not backpatching though, since this is just a marginal performance issue rather than a real bug.
-
由 Tom Lane 提交于
subquery output column exactly once left-to-right. Although this is the case in the original parser output, it might not be so after rewriting and constant-folding, as illustrated by bug #3882 from Jan Mate. Instead scan the subquery's target list to obtain needed per-column information; this is duplicative of what the parser did, but only a couple dozen lines need be copied, and we can clean up a couple of notational uglinesses. Bug was introduced in 8.2 as part of revision of SubLink representation.
-
由 Tom Lane 提交于
constraint, the constraint is renamed as well. This avoids inconsistent situations that could confuse pg_dump (not to mention humans). We might at some point provide ALTER TABLE RENAME CONSTRAINT as a more general solution, but there seems no reason not to allow doing it this way too. Per bug #3854 and related discussions.
-
由 Bruce Momjian 提交于
Jun Kuwamura
-
- 17 1月, 2008 5 次提交
-
-
由 Magnus Hagander 提交于
Erik Rijkers
-
由 Magnus Hagander 提交于
Marko Kreen
-
由 Andrew Dunstan 提交于
-
由 Tom Lane 提交于
the PATH responsive to the installation prefix, which was the apparent intent of the previous edit, but not well executed.
-
由 Bruce Momjian 提交于
-
- 16 1月, 2008 4 次提交
-
-
由 Teodor Sigaev 提交于
fixed length arrays to prevent array's overrun. Per report by Hannes Dorbath <light@theendofthetunnel.de> and comments by Tom.
-
由 Tom Lane 提交于
ParameterStatus message can be sent during COPY OUT: it's definitely possible, since COPY from a SELECT subquery can trigger any user-defined function.
-
由 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.
-