summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
2008-03-10Add a CaseSensitive parameter to synonym dictionaries.Tom Lane
Simon Riggs
2008-03-09Remove postmaster.c's check that NBuffers is at least twice MaxBackends.Tom Lane
With the addition of multiple autovacuum workers, our choices were to delete the check, document the interaction with autovacuum_max_workers, or complicate the check to try to hide that interaction. Since this restriction has never been adequate to ensure backends can't run out of pinnable buffers, it doesn't really have enough excuse to live to justify the second or third choices. Per discussion of a complaint from Andreas Kling (see also bug #3888). This commit also removes several documentation references to this restriction, but I'm not sure I got them all.
2008-03-08Add:Bruce Momjian
> > * Consider a function-based API for '@@' full text searches > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php >
2008-03-07Add:Bruce Momjian
> > * Add a function like pg_get_indexdef() that report more detailed index > information > > http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php >
2008-03-07Add:Bruce Momjian
> > > o Prevent autovacuum from running if an old transaction is still > running from the last vacuum > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php >
2008-03-07Added to TODO:Bruce Momjian
> > * Allow text search dictionary to filter out only stop words > > http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php
2008-03-07Add to TODO:Bruce Momjian
> > * Consider allowing higher priority queries to have referenced buffer > cache pages stay in memory longer > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php
2008-03-07Add:Bruce Momjian
> > * Improve referential integrity checks > > http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php
2008-03-07Add item: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
2008-03-07Add URL for: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
2008-03-07Add:Bruce Momjian
> o Add SQLSTATE severity to PGconn return status > > http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php
2008-03-07Add:Bruce Momjian
> o Have \l+ show database size, if permissions allow > > Ideally it will not generate an error for invalid permissions >
2008-03-07Add: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. >
2008-03-07Clearify PITR doc wording.Bruce Momjian
2008-03-07Update wording:Bruce Momjian
< o Require all check constraints to be inherited > o Require all CHECK constraints to be inherited
2008-03-07Add:Bruce Momjian
> > o Require all check constraints to be inherited > > http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php
2008-03-07Add: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
2008-03-06Add URL for: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
2008-03-06Add URL for:Bruce Momjian
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-patches/2007-03/msg00139.php
2008-03-06Add URLs for: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 >
2008-03-06Add URL for:Bruce Momjian
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01375.php
2008-03-06Document that enabling asserts can _significantly_ slow down the server.Bruce Momjian
Back patch to 8.3.X.
2008-03-06Add: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.
2008-03-06Document use of pg_locks.objid for advisory locks, suggestion from Marc MaminBruce Momjian
2008-03-06Add:Bruce Momjian
> > * Reduce memory usage of aggregates in set returning functions > > http://archives.postgresql.org/pgsql-performance/2008-01/msg00031.php >
2008-03-06Add:Bruce Momjian
> > o Prevent escape string warnings when object names have > backslashes > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00227.php >
2008-03-06Add: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
2008-03-06Move client encoding libpq function docs into libpq doc section, andBruce Momjian
just reference them from the localization doc section. Backpatch to 8.3.X.
2008-03-06Wording fix:Bruce Momjian
< o Have CONSTRAINT cname NOT NULL preserve the contraint name > o Have CONSTRAINT cname NOT NULL record the contraint name
2008-03-06Add: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 >
2008-03-06Break out referential integrity and server-side languages into separateBruce Momjian
TODO categories.
2008-03-05Document that increasing the number of checkpoints segments orBruce Momjian
checkpoint timeout can incrase the time needed for crash recovery, per suggestion from Simon.
2008-03-05Add URL for:Bruce Momjian
* Add support for SQL-standard GENERATED/IDENTITY columns > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00604.php
2008-03-05Add URL for:Bruce Momjian
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00642.php >
2008-03-05Add:Bruce Momjian
> > o Allow COPY FROM to create index entries in bulk > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php >
2008-03-04Update pg_dump item: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.
2008-03-04Show example of ts_headline() using a configuration name.Bruce Momjian
2008-03-04Remove:Bruce Momjian
< < o To better utilize resources, restore data, primary keys, and < indexes for a single table before restoring the next table < < Hopefully this will allow the CPU-I/O load to be more uniform < for simultaneous restores. The idea is to start data restores < for several objects, and once the first object is done, to move < on to its primary keys and indexes. Over time, simultaneous < data loads and index builds will be running.
2008-03-04Add URL for:Bruce Momjian
o Allow pg_restore to utilize multiple CPUs and I/O channels by restoring multiple objects simultaneously > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php
2008-03-04Add ideas for concurrent pg_dump and pg_restore:Bruce Momjian
< * pg_dump > * pg_dump / pg_restore > o Allow pg_dump to utilize multiple CPUs and I/O channels by dumping > multiple objects simultaneously > > The difficulty with this is getting multiple dump processes to > produce a single dump output file. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php > > o Allow pg_restore to utilize multiple CPUs and I/O channels by > restoring multiple objects simultaneously > > This might require a pg_restore flag to indicate how many > simultaneous operations should be performed. Only pg_dump's > -Fc format has the necessary dependency information. > > o To better utilize resources, restore data, primary keys, and > indexes for a single table before restoring the next table > > Hopefully this will allow the CPU-I/O load to be more uniform > for simultaneous restores. The idea is to start data restores > for several objects, and once the first object is done, to move > on to its primary keys and indexes. Over time, simultaneous > data loads and index builds will be running. > > o To better utilize resources, allow pg_restore to check foreign > keys simultaneously, where possible > o Allow pg_restore to create all indexes of a table > concurrently, via a single heap scan > > This requires a pg_dump -Fc file because that format contains > the required dependency information. > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php > > o Allow pg_restore to load different parts of the COPY data > simultaneously < single heap scan, and have a restore of a pg_dump somehow use it > single heap scan, and have pg_restore use it < http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
2008-03-03Update Japanese FAQ.Bruce Momjian
Jun Kuwamura
2008-03-03Add:Bruce Momjian
> * Allow INSERT ... DELETE ... RETURNING, namely allow the DELETE ... > RETURNING to supply values to the INSERT > http://archives.postgresql.org/pgsql-hackers/2008-02/thrd2.php#00979
2008-03-03Add another URL for:Bruce Momjian
o Consider using a ring buffer for COPY FROM < < http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php
2008-03-03Document that REVOKE doesn't remove all permissions if PUBLIC has permissions.Bruce Momjian
2008-03-03Add:Bruce Momjian
> > * Allow the UUID type to accept non-standard formats > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01214.php
2008-03-03Add:Bruce Momjian
> * Speed WAL recovery by allowing more than one page to be prefetched > > This involves having a separate process that can be told which pages > the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php >
2008-03-03Remove "reliably" from chr(0) doc mention.Bruce Momjian
2008-03-03Document that chr(0) is not supported, and why.Bruce Momjian
2008-03-03Fix markup.Bruce Momjian
2008-03-03Add new FAQ item:Bruce Momjian
<H3 id="item1.15">1.15) How do I unsubscribe from the PostgreSQL email lists? How do I avoid receiving duplicate emails?</H3>
generated by cgit v1.2.3 (git 2.46.0) at 2025-12-07 22:15:49 +0000