- 14 9月, 2004 6 次提交
-
-
由 Tom Lane 提交于
Claudio Natoli
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Neil Conway 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
mode see a fresh snapshot for each command in the function, rather than using the latest interactive command's snapshot. Also, suppress fresh snapshots as well as CommandCounterIncrement inside STABLE and IMMUTABLE functions, instead using the snapshot taken for the most closely nested regular query. (This behavior is only sane for read-only functions, so the patch also enforces that such functions contain only SELECT commands.) As per my proposal of 6-Sep-2004; I note that I floated essentially the same proposal on 19-Jun-2002, but that discussion tailed off without any action. Since 8.0 seems like the right place to be taking possibly nontrivial backwards compatibility hits, let's get it done now.
-
- 13 9月, 2004 9 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Neil Conway 提交于
-
由 Bruce Momjian 提交于
it and have it in case we need it for some special case.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
sure to clean up the already-created lock object, if it has no other references. Avoids possibly-permanent leak of shared memory.
-
- 12 9月, 2004 1 次提交
-
-
由 Tom Lane 提交于
((Snapshot) NULL) can no longer be confused with a valid snapshot, as per my recent suggestion. Define a macro InvalidSnapshot for 0. Use InvalidSnapshot instead of SnapshotAny as the do-nothing special case for heap_update and heap_delete crosschecks; this seems a little cleaner even though the behavior is really the same.
-
- 11 9月, 2004 7 次提交
-
-
由 Tom Lane 提交于
will be cleaned up at end of transaction, even when there is no other LO operation in the transaction. Per bug report from Daniel Schuchardt.
-
由 Bruce Momjian 提交于
than /dev/null, which Win32 doesn't have.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Have AFTER triggers execute after the appropriate SQL statement in a > * -Have AFTER triggers execute after the appropriate SQL statement in a
-
由 Tom Lane 提交于
as per bug #1249; and remove the last vestiges of using \connect to change authorization.
-
由 Tom Lane 提交于
rather than when returning to the idle loop. This makes no particular difference for interactively-issued queries, but it makes a big difference for queries issued within functions: trigger execution now occurs before the calling function is allowed to proceed. This responds to numerous complaints about nonintuitive behavior of foreign key checking, such as http://archives.postgresql.org/pgsql-bugs/2004-09/msg00020.php, and appears to be required by the SQL99 spec. Also take the opportunity to simplify the data structures used for the pending-trigger list, rename them for more clarity, and squeeze out a bit of space.
-
由 Bruce Momjian 提交于
> * Make row-wise comparisons work per SQL spec >
-
- 10 9月, 2004 15 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Remove Win32 rename/unlink looping if unnecessary
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
-
由 Neil Conway 提交于
-It fixes up some bugs with handling setval calls -Adds upgrade instructions from prior versions -Improved the sample config file -Fixed some things in the clean_pending script
-
由 Neil Conway 提交于
name first, make sure \di+ shows description last, and make \dl SQL look a little more standard.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 09 9月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
pgtest.
-