- 27 6月, 2006 1 次提交
-
-
由 Tom Lane 提交于
will be expanded to a list of their member fields, rather than creating a nested rowtype field as formerly. (The old behavior is still available by omitting '.*'.) This syntax is not allowed by the SQL spec AFAICS, so changing its behavior doesn't violate the spec. The new behavior is substantially more useful since it allows, for example, triggers to check for data changes with 'if row(new.*) is distinct from row(old.*)'. Per my recent proposal.
-
- 26 6月, 2006 9 次提交
-
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
relevant location.
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
> * Bruce is Bruce Momjian <bruce@momjian.us> of EnterpriseDB
-
由 Tom Lane 提交于
palloc() will normally round allocation requests up to the next power of 2, so make dynahash choose allocation sizes that are as close to a power of 2 as possible. Back-patch to 8.1 --- the problem exists further back, but a much larger patch would be needed and it doesn't seem worth taking any risks.
-
由 Bruce Momjian 提交于
< * Reuse index tuples that point to rows that are not visible to anyone? > * Reuse index tuples that point to heap tuples that are not visible to > anyone?
-
- 25 6月, 2006 7 次提交
-
-
由 Michael Meskes 提交于
-
由 Alvaro Herrera 提交于
opposed to what other versions apparently do, so it's not safe to print an error message. Besides, getopt_long itself already did, so it's redundant anyway.
-
由 Bruce Momjian 提交于
PGDG: > Yes. In fact the copyright belongs to credativ GmbH the company that > paid Carsten for his work. As you may or may not know I'm the CEO of > that company and can assure you that his work was contributed to the > PostgreSQL project.
-
由 Bruce Momjian 提交于
Magnus Hagander
-
由 Bruce Momjian 提交于
After updating to the latest cvs, and also building most of the addons (like PLs), the following patch is neededf for win32 + Visual C++. * Switch to use the new win32 semaphore code * Rename win32_open to pgwin32_open. win32_open collides with symbols defined in Perl. MingW didn't detect ig, MSVC did. And it's a bit too generic a name to export globally, imho... * Python defines some partially broken #pragmas in the headers when doing a debug build. Workaround. Magnus Hagander
-
由 Bruce Momjian 提交于
< * Allow heap reuse of UPDATEd rows if old and new versions are on the < same heap page? > * Allow heap reuse of UPDATEd rows if no indexed columns are changed, > and old and new versions are on the same heap page? < This is possible for same-page updates because a single index row < can point to both old and new values. > While vacuum handles DELETEs fine, updating of non-indexed columns, like > counters, are difficult for VACUUM to handle efficiently. This method > is possible for same-page updates because a single index row can be > used to point to both old and new values.
-
由 Bruce Momjian 提交于
> > * Allow heap reuse of UPDATEd rows if old and new versions are on the > same heap page? > > This is possible for same-page updates because a single index row > can point to both old and new values. > http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
-
- 24 6月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 23 6月, 2006 3 次提交
-
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
and there was some question about its copyright status.
-
由 Tom Lane 提交于
backup history file. Bug introduced by the 8.1 change to make pg_stop_backup delete older history files. Per report from Masao Fujii.
-
- 22 6月, 2006 7 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
setup_win32_locks() call formerly was, to ensure that cancelConnLock is valid when it needs to be. Per Yoshiyuki Asaba.
-
由 Tom Lane 提交于
aggregates. We just disallowed that, and AFAICS there should be no other cases where direct (non-aggregated) references to input columns are allowed in a query with aggregation and no GROUP BY.
-
由 Tom Lane 提交于
This is disallowed by the SQL spec because it doesn't have any very sensible interpretation. Historically Postgres has allowed it but behaved strangely. As of PG 8.1 a server crash is possible if the MIN/MAX index optimization gets applied; rather than try to "fix" that, it seems best to just enforce the spec restriction. Per report from Josh Drake and Alvaro Herrera.
-
由 Tom Lane 提交于
Eliminate a gratuitously different wording of the 'cannot use aggregate function in check constraint' error message.
-
由 Joe Conway 提交于
initially be 0. This is needed as a previous ABORT might have wiped out an automatically opened transaction without maintaining the cursor count. - Fix regression test expected file for the correct ERROR message, which we now get given the above bug fix.
-
由 Tom Lane 提交于
GetVariable() and be consistent about treatment of the list header. Motivated by noticing strspn() taking an unreasonable percentage of runtime --- the call removed from GetVariable() was the only one that could be in a high-usage path ...
-
- 21 6月, 2006 5 次提交
-
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
Added missing error handling in a few functions in ecpglib
-
由 Tom Lane 提交于
changing semantics too much. statement_timestamp is now set immediately upon receipt of a client command message, and the various places that used to do their own gettimeofday() calls to mark command startup are referenced to that instead. I have also made stats_command_string use that same value for pg_stat_activity.query_start for both the command itself and its eventual replacement by <IDLE> or <idle in transaction>. There was some debate about that, but no argument that seemed convincing enough to justify an extra gettimeofday() call.
-
由 Tom Lane 提交于
libpq/md5.h, so that there's a clear separation between backend-only definitions and shared frontend/backend definitions. (Turns out this is reversing a bad decision from some years ago...) Fix up references to crypt.h as needed. I looked into moving the code into src/port, but the headers in src/include/libpq are sufficiently intertwined that it seems more work than it's worth to do that.
-
- 20 6月, 2006 1 次提交
-
-
由 Tom Lane 提交于
functions.
-
- 19 6月, 2006 6 次提交
-
-
由 Michael Meskes 提交于
<joachim.wieland@credativ.de>
-
由 Tom Lane 提交于
current commands; instead, store current-status information in shared memory. This substantially reduces the overhead of stats_command_string and also ensures that pg_stat_activity is fully up to date at all times. Per my recent proposal.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
for it. Hopefully will fix core dump evidenced by some buildfarm members since fadvise patch went in. The actual definition of the function is not ABI-compatible with compiler's default assumption in the absence of any declaration, so it's clearly unsafe to try to call it without seeing a declaration.
-
由 Tom Lane 提交于
Darwin's libedit; per my proposal last August. Also, suppress cast-away- const warnings.
-
由 Tom Lane 提交于
We have once or twice seen failures suggesting that control didn't get to the exception block before the timeout elapsed, which is unlikely but not impossible in a parallel regression test (with a dozen other backends competing for cycles). This change doesn't completely prevent the problem of course, but it should reduce the probability enough that we don't see it anymore. Per buildfarm results.
-