- 08 3月, 2008 4 次提交
-
-
由 Bruce Momjian 提交于
> > * Improve referential integrity checks > > http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php
-
由 Bruce Momjian 提交于
> o Store per-table autovacuum settings in pg_class.reloptions. > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg01440.php > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00724.php
-
由 Bruce Momjian 提交于
* Allow multiple identical NOTIFY events to always be communicated to the client, rather than sent as a single notification to the listener http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
-
由 Bruce Momjian 提交于
> o Add SQLSTATE severity to PGconn return status > > http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php
-
- 07 3月, 2008 19 次提交
-
-
由 Tom Lane 提交于
TopMemoryContext, rather than scattered through executor per-query contexts. This poses no danger of memory leak since the ResourceOwner mechanism guarantees release of no-longer-needed items. It is needed because the per-query context might already be released by the time we try to clean up the hash scan list. Report by ykhuang, diagnosis by Heikki. Back-patch to 8.0, where the ResourceOwner-based cleanup was introduced. The given test case does not fail before 8.2, probably because we rearranged transaction abort processing somehow; but this coding is undoubtedly risky so I'll patch 8.0 and 8.1 anyway.
-
由 Bruce Momjian 提交于
> o Have \l+ show database size, if permissions allow > > Ideally it will not generate an error for invalid permissions >
-
由 Bruce Momjian 提交于
> > * Add comments on system tables/columns using the information in > catalogs.sgml > > Ideally the information would be pulled from the SGML file > automatically. >
-
由 Teodor Sigaev 提交于
a unused memory holes in tsquery. Per report by Richard Huxton <dev@archonet.com>. It was working well because in fact tsquery->size is not used for any kind of operation except comparing tsqueries. So, in HEAD it's enough to fix to_tsquery function, but for previous version it's needed to remove optimization in CompareTSQ to prevent requirement of renew all stored tsquery.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< o Require all check constraints to be inherited > o Require all CHECK constraints to be inherited
-
由 Bruce Momjian 提交于
> > o Require all check constraints to be inherited > > http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php
-
由 Bruce Momjian 提交于
> o Have \d show foreign keys that reference a table's primary key > > http://archives.postgresql.org/pgsql-hackers/2007-04/msg00424.php > > o Have \d show child tables that inherit from the specified parent
-
由 Bruce Momjian 提交于
* Consider compressing indexes by storing key values duplicated in several rows as a single index entry > http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php
-
由 Bruce Momjian 提交于
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-patches/2007-03/msg00139.php
-
由 Bruce Momjian 提交于
* Consider compressing indexes by storing key values duplicated in several rows as a single index entry > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php > http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php > http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php >
-
由 Bruce Momjian 提交于
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01375.php
-
由 Bruce Momjian 提交于
Back patch to 8.3.X.
-
由 Bruce Momjian 提交于
> > * Allow client certificate names to be checked against the client > hostname > > This is already implemented in > libpq/fe-secure.c::verify_peer_name_matches_certificate() but the code > is commented out.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> > * Reduce memory usage of aggregates in set returning functions > > http://archives.postgresql.org/pgsql-performance/2008-01/msg00031.php >
-
由 Bruce Momjian 提交于
> > o Prevent escape string warnings when object names have > backslashes > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00227.php >
-
由 Bruce Momjian 提交于
> * Prevent malicious functions from being executed with the permissions > of unsuspecting users > > Index functions are safe, so VACUUM and ANALYZE are safe too. > Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable. > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php
-
由 Bruce Momjian 提交于
-
- 06 3月, 2008 11 次提交
-
-
由 Bruce Momjian 提交于
just reference them from the localization doc section. Backpatch to 8.3.X.
-
由 Bruce Momjian 提交于
< o Have CONSTRAINT cname NOT NULL preserve the contraint name > o Have CONSTRAINT cname NOT NULL record the contraint name
-
由 Bruce Momjian 提交于
> > o Have CONSTRAINT cname NOT NULL preserve the contraint name > > Right now pg_attribute.attnotnull records the NOT NULL status > of the column, but does not record the contraint name >
-
由 Bruce Momjian 提交于
TODO categories.
-
由 Alvaro Herrera 提交于
-
由 Alvaro Herrera 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
caches that we don't actually need to touch. This saves some trivial number of cycles and avoids certain cases of deadlock when doing concurrent VACUUM FULL on system catalogs. Per report from Gavin Roy. Backpatch to 8.2. In earlier versions, CatalogCacheInitializeCache didn't lock the relation so there's no deadlock risk (though that certainly had plenty of risks of its own).
-
由 Bruce Momjian 提交于
checkpoint timeout can incrase the time needed for crash recovery, per suggestion from Simon.
-
由 Bruce Momjian 提交于
* Add support for SQL-standard GENERATED/IDENTITY columns > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00604.php
-
由 Bruce Momjian 提交于
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00642.php >
-
- 05 3月, 2008 4 次提交
-
-
由 Bruce Momjian 提交于
> > o Allow COPY FROM to create index entries in bulk > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php >
-
由 Bruce Momjian 提交于
maximum number of bytes allowed.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
temporary table; we can't support that because there's no way to clean up the source backend's internal state if the eventual COMMIT PREPARED is done by another backend. This was checked correctly in 8.1 but I broke it in 8.2 :-(. Patch by Heikki Linnakangas, original trouble report by John Smith.
-
- 04 3月, 2008 2 次提交
-
-
由 Magnus Hagander 提交于
Dave Page
-
由 Bruce Momjian 提交于
< produce a single dump output file. > produce a single dump output file. It also would require > several sessions to share the same snapshot.
-