- 18 8月, 2004 3 次提交
-
-
由 Bruce Momjian 提交于
< * -Allow savepoints / nested transactions [transactions] (Alvaro) > * -Allow savepoints / nested transactions (Alvaro) 348a349,353 > * Add an option to automatically use savepoints for each statement in a > multi-statement transaction. > > When enabled, this would allow errors in multi-statement transactions > to be automatically ignored.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Always create thread-specific variable.
-
- 17 8月, 2004 9 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
global variables are problematic on this platform. Simplest solution seems to be to initialize pthread key variable to 0. Also, rename this variable and check_sigpipe_handler to something involving "pq" to avoid gratuitous pollution of application namespace.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
rename/unlink defined later. Problem exists on MS VC. Andrew Francis
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
> o Add ALTER INDEX syntax to work like ALTER TABLE indexname
-
- 16 8月, 2004 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Set proper permissions on non-system schemas during db creation > > Currently all schemas are owned by the super-user because they are > copied from the template1 database. >
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
proposals by Oliver Jowett. Update documentation.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
of XLogInsert had the same sort of checkpoint interlock problem as RecordTransactionCommit, and indeed I found some. Btree index build and ALTER TABLE SET TABLESPACE write data outside the friendly confines of the buffer manager, and therefore they have to take their own responsibility for checkpoint interlock. The easiest solution seems to be to force smgrimmedsync at the end of the index build or table copy, even when the operation is being WAL-logged. This is sufficient since the new index or table will be of interest to no one if we don't get as far as committing the current transaction.
-
由 Tom Lane 提交于
therefore starting with GetCurrentTransactionId is wrong. Fixes miscomputation of RecentGlobalXmin leading to bizarre behavior reported by Gavin Sherry.
-
- 15 8月, 2004 8 次提交
-
-
由 Tom Lane 提交于
Oliver Jowett.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
mode isn't really serializable. I had thought this was covered already in our docs, but I sure can't find it.
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
- 14 8月, 2004 10 次提交
-
-
由 Bruce Momjian 提交于
> > * Allow buffered WAL writes and fsync > > Instead of guaranteeing recovery of all committed transactions, this > would provide improved performance by delaying WAL writes and fsync > so an abrupt operating system restart might lose a few seconds of > committed transactions but still be consistent. We could perhaps > remove the 'fsync' parameter (which results in an an inconsistent > database) in favor of this capability.
-
由 Tom Lane 提交于
Andrew Dunstan, some further hacking by Tom Lane.
-
由 Tom Lane 提交于
logic a little bit.
-
由 Tom Lane 提交于
in plpgsql, particularly trying to begin/end/rollback a transaction.
-
由 Tom Lane 提交于
back branches later.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
- 13 8月, 2004 3 次提交
-
-
由 Tom Lane 提交于
patches.
-
由 Tom Lane 提交于
don't hold an open file reference to the original table at the end. This is a good thing in any case, particularly so on Windows which cannot drop the table file otherwise.
-
由 Bruce Momjian 提交于
-