- 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 6 次提交
-
-
由 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.
-
由 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.
-