- 08 1月, 2006 4 次提交
-
-
由 Neil Conway 提交于
access information about the prepared statements that are available in the current session. Original patch from Joachim Wieland, various improvements by Neil Conway. The "statement" column of the view contains the literal query string sent by the client, without any rewriting or pretty printing. This means that prepared statements created via SQL will be prefixed with "PREPARE ... AS ", whereas those prepared via the FE/BE protocol will not. That is unfortunate, but discussion on -patches did not yield an efficient way to improve this, and there is some merit in returning exactly what the client sent to the backend. Catalog version bumped, regression tests updated.
-
由 Tom Lane 提交于
use it. While it normally has been opened earlier during btree index build, testing shows that it's possible for the link to be closed again if an sinval reset occurs while the index is being built.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
dead and have become unreferenced. Before 8.1, such members were left for AtEOXact_CatCache() to clean up, but now AtEOXact_CatCache isn't supposed to have anything to do. In an assert-enabled build this bug leads to an assertion failure at transaction end, but in a non-assert build the dead member is effectively just a small memory leak. Per report from Jeremy Drake.
-
- 07 1月, 2006 2 次提交
-
-
由 Tom Lane 提交于
an INSERT target list during rule rewriting. Per report from John Supplee.
-
由 Bruce Momjian 提交于
-
- 06 1月, 2006 11 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
rather than elog(FATAL), when there is no more room in ShmemBackendArray. This is a security issue since too many connection requests arriving close together could cause the postmaster to shut down, resulting in denial of service. Reported by Yoshiyuki Asaba, fixed by Magnus Hagander.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
The consequences of overwriting a non-empty page are bad enough that we should not omit this test in production builds.
-
由 Tom Lane 提交于
the relation but it finds a pre-existing valid buffer. The buffer does not correspond to any page known to the kernel, so we *must* do smgrextend to ensure that the space becomes allocated. The 7.x branches all do this correctly, but the corner case got lost somewhere during 8.0 bufmgr rewrites. (My fault no doubt :-( ... I think I assumed that such a buffer must be not-BM_VALID, which is not so.)
-
由 Bruce Momjian 提交于
> > * Allow SERIAL sequences to inherit permissions from the base table?
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< stable logging probably can not have indexes. [wallog] > stable logging probably can not have indexes. [walcontrol]
-
由 Bruce Momjian 提交于
< STABLE | DEFAULT ]. [wallog] > STABLE | DEFAULT ]. Tables using non-default logging should not use > referential integrity with default-logging tables, and tables using > stable logging probably can not have indexes. [wallog]
-
由 Bruce Momjian 提交于
< the table. Another option is to avoid transaction logging entirely < and truncate or drop the table on crash recovery. These should be < implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | < TRUNCATE | STABLE | DEFAULT ]. [wallog] > the table. This would affect COPY, and perhaps INSERT/UPDATE too. > Another option is to avoid transaction logging entirely and truncate > or drop the table on crash recovery. These should be implemented > using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | > STABLE | DEFAULT ]. [wallog]
-
由 Bruce Momjian 提交于
> > * Allow control over which tables are WAL-logged > > Allow tables to bypass WAL writes and just fsync() dirty pages on > commit. To do this, only a single writer can modify the table, and > writes must happen only on new pages. Readers can continue accessing > the table. Another option is to avoid transaction logging entirely > and truncate or drop the table on crash recovery. These should be > implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | > TRUNCATE | STABLE | DEFAULT ]. [wallog]
-
- 05 1月, 2006 15 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * %Remove behavior of postmaster -o after making postmaster/postgres < flags unique > * %Remove behavior of postmaster -o
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
http://archives.postgresql.org/pgsql-hackers/2006-01/msg00151.php for the complete plan.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * -Remove BeOS and QNX-specific code
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
an LWLock instead of a spinlock. This hardly matters on Unix machines but should improve startup performance on Windows (or any port using EXEC_BACKEND). Per previous discussion.
-
由 Tom Lane 提交于
expressional indexes. Per report from Brian Hirt.
-
- 04 1月, 2006 6 次提交
-
-
由 Tom Lane 提交于
This makes the salt space for md5 and xdes algorithms a lot smaller than it should be. Marko Kreen
-
由 Joe Conway 提交于
than the local query specifies (e.g. in the FROM clause), throw an ERROR (instead of crashing). Fix for bug #2129 reported by Akio Iwaasa.
-
由 Tom Lane 提交于
per http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343616 via Martin Pitt.
-
由 Tom Lane 提交于
returning the rowtype it's supposed to return. Per reports from David Niblett and Michael Fuhr.
-
由 Bruce Momjian 提交于
optimization.
-
由 Bruce Momjian 提交于
call for every stats packet read to adjust select() timeout. Other stylistic improvements.
-
- 03 1月, 2006 2 次提交