summaryrefslogtreecommitdiff
path: root/doc/src/FAQ
AgeCommit message (Collapse)Author
2007-09-07Add Hash thread URL:Bruce Momjian
> http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php
2007-09-05Done:Bruce Momjian
< * Reduce XID consumption of read-only queries < < http://archives.postgresql.org/pgsql-hackers/2007-08/msg00516.php < < > * -Reduce XID consumption of read-only queries
2007-08-28Please ignore. Fresh checkout to see if this fixes it.Bruce Momjian
2007-08-28Commit test, please ignore.Bruce Momjian
2007-08-28CVS commit test for TODO. Please ignore.Bruce Momjian
2007-08-28Small commit test for TODO.Bruce Momjian
2007-08-28Update TODO.html.Bruce Momjian
2007-08-28Batch of TODO updates, mostly completed item marking and whitespaceBruce Momjian
fixes. Not sure how these weren't comitted before.
2007-08-23Fix typo in FAQ_DEV.Bruce Momjian
2007-08-23Add book to FAQ_DEV:Bruce Momjian
Transactional Information Systems by Gerhard Weikum, Kaufmann
2007-08-19Done:Bruce Momjian
< * Allow server log information to be output as INSERT statements > * -Allow server log information to be output as CSV format
2007-08-16Add:Bruce Momjian
> > * Reduce XID consumption of read-only queries > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00516.php >
2007-08-15Add third idea about pulling data from indexes.Bruce Momjian
> A third idea would be for a heap scan to check if all rows are visible > and if so set a per-table flag which can be checked by index scans. > Any change to the table would have to clear the flag. To detect > changes during the heap scan a counter could be set at the start and > checked at the end --- if it is the same, the table has not been > modified --- any table change would increment the counter.
2007-08-15Fix whitespace in TODO.Bruce Momjian
2007-08-14Done for ecpg:Bruce Momjian
< o Use backend PREPARE/EXECUTE facility for ecpg where possible
2007-08-01Done:Bruce Momjian
< * Allow buffered WAL writes and fsync
2007-07-18Add:Bruce Momjian
> > o Allow GLOBAL temporary tables to exist as empty by default in > all sessions > > http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php >
2007-07-17Remove http://www.benchmarkresources.com, no longer resolves to aBruce Momjian
meaningful site.
2007-07-17Add:Bruce Momjian
> * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
2007-07-08Remove, per Magnus:Bruce Momjian
< o Check WSACancelBlockingCall() for interrupts [win32intr]
2007-06-28Done:Bruce Momjian
> * -Reduce checkpoint performance degredation by forcing data to disk
2007-06-13Update item:Bruce Momjian
< * Allow EXPLAIN output to be more easily processed by scripts > * Allow EXPLAIN output to be more easily processed by scripts, perhaps XML
2007-06-11Done:Bruce Momjian
< o Allow UPDATE/DELETE WHERE CURRENT OF cursor < < This requires using the row ctid to map cursor rows back to the < original heap row. This become more complicated if WITH HOLD cursors < are to be supported because WITH HOLD cursors have a copy of the row < and no FOR UPDATE lock. < http://archives.postgresql.org/pgsql-hackers/2007-01/msg01014.php < > o -Allow UPDATE/DELETE WHERE CURRENT OF cursor
2007-06-08Done:Bruce Momjian
< * Allow sequential scans to take advantage of other concurrent > * -Allow sequential scans to take advantage of other concurrent < < One possible implementation is to start sequential scans from the lowest < numbered buffer in the shared cache, and when reaching the end wrap < around to the beginning, rather than always starting sequential scans < at the start of the table. < < http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php < http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php < http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00415.php <
2007-06-03Remove description for:Bruce Momjian
o -Add a GUC variable to control the tablespace for temporary objects and sort files < < It could start with a random tablespace from a supplied list and < cycle through the list. <
2007-06-02Re-add TODO and clarify it is for the kernel cache:Bruce Momjian
< * Allow free-behind capability for large sequential scans, perhaps using < posix_fadvise() > * Allow free-behind capability for large sequential scans to avoid > kernel cache spoiling
2007-06-02TODO item not needed anymore now that the buffer cache isBruce Momjian
scan-resistant: < < * Allow free-behind capability for large sequential scans, perhaps using < posix_fadvise() < < Posix_fadvise() can control both sequential/random file caching and < free-behind behavior, but it is unclear how the setting affects other < backends that also have the file open, and the feature is not supported < on all operating systems.
2007-06-01Add URL for:Bruce Momjian
o Research self-referential UPDATEs that see inconsistent row versions in read-committed mode < > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00016.php
2007-06-01Update wording:Bruce Momjian
o Research self-referential UPDATEs that see inconsistent row versions in read-committed mode http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php
2007-06-01Wording improvement.Bruce Momjian
2007-06-01Update FAQ_DEV URL to output for text format.Bruce Momjian
2007-06-01Add URL for code comments to developer's FAQ:Bruce Momjian
http://www.ibm.com/developerworks/linux/library/l-clear-code/?ca=dgr-FClnxw01linuxcodetips
2007-05-30Update:Bruce Momjian
< * Consider allowing 64-bit integers to be passed by value on 64-bit < platforms > * Consider allowing 64-bit integers and floats to be passed by value on > 64-bit platforms > > Also change 32-bit floats (float4) to be passed by value at the same > time. >
2007-05-30Fix wording:Bruce Momjian
< * Consider allowing 64-bit integers to be passed by reference on 64-bit > * Consider allowing 64-bit integers to be passed by value on 64-bit
2007-05-30Add:Bruce Momjian
> > * Consider allowing 64-bit integers to be passed by reference on 64-bit > platforms
2007-05-30Add URL for:Bruce Momjian
* Improve speed with indexes For large table adjustments during VACUUM FULL, it is faster to cluster or reindex rather than update the index. Also, index updates can bloat the index.
2007-05-28Update wording:Bruce Momjian
< * Fix self-referential UPDATEs seeing inconsistent row versions in > * Fix self-referential UPDATEs that see inconsistent row versions in
2007-05-28Add:Bruce Momjian
> > * Fix self-referential UPDATEs seeing inconsistent row versions in > read-committed mode > > http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php
2007-05-18Done:Bruce Momjian
< * Fix problem with excessive logging during SSL disconnection > * -Fix problem with excessive logging during SSL disconnection
2007-05-17dded to TODO:Bruce Momjian
> > * Support scoped IPv6 addresses > > http://archives.postgresql.org/pgsql-bugs/2007-05/msg00111.php
2007-05-17Add URL for:Bruce Momjian
* Implement the SQL standard mechanism whereby REVOKE ROLE revokes only the privilege granted by the invoking role, and not those granted by other roles > > http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php
2007-05-17Add, per Alvaro:Bruce Momjian
> > * Implement the SQL standard mechanism whereby REVOKE ROLE revokes only > the privilege granted by the invoking role, and not those granted > by other roles
2007-05-17Add:Bruce Momjian
> > * Fix problem with excessive logging during SSL disconnection > > http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php > http://archives.postgresql.org/pgsql-bugs/2007-05/msg00065.php
2007-05-15Add URLs for:Bruce Momjian
* Add support for SQL-standard GENERATED/IDENTITY columns > http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php > http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php
2007-05-14Update instructions on creating TODO entry.Bruce Momjian
2007-05-13Mark as done, add URL for other item:Bruce Momjian
< o Add support for arrays of complex types > > http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php > > o -Add support for arrays of complex types
2007-05-12Add:Bruce Momjian
> * Have configure choose integer datetimes by default > > http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php
2007-05-12Add:Bruce Momjian
> o Allow data to be passed in native language formats, rather > than only text > http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php
2007-05-05Done:Bruce Momjian
< Last updated: Sat May 5 10:47:39 EDT 2007 > Last updated: Sat May 5 11:39:57 EDT 2007 < * Flush cached query plans when the dependent objects change, < when the cardinality of parameters changes dramatically, or > * -Flush cached query plans when the dependent objects change or < < A more complex solution would be to save multiple plans for different < cardinality and use the appropriate plan based on the EXECUTE values. < < * Track dependencies in function bodies and recompile/invalidate < < This is particularly important for references to temporary tables < in PL/PgSQL because PL/PgSQL caches query plans. The only workaround < in PL/PgSQL is to use EXECUTE. One complexity is that a function < might itself drop and recreate dependent tables, causing it to < invalidate its own query plan. < < * Invalidate prepared queries, like INSERT, when the table definition > * -Track dependencies in function bodies and recompile/invalidate > * -Invalidate prepared queries, like INSERT, when the table definition
2007-05-05Move item:Bruce Momjian
< * Invalidate prepared queries, like INSERT, when the table definition < is altered > > * Invalidate prepared queries, like INSERT, when the table definition > is altered
generated by cgit v1.2.3 (git 2.46.0) at 2025-10-01 17:48:45 +0000