summaryrefslogtreecommitdiff
path: root/doc/src/FAQ
AgeCommit message (Collapse)Author
2007-02-20Add for WIN32:Bruce Momjian
< > o Check .pgpass file permissions
2007-02-20Add:Bruce Momjian
> * Fix IS OF so it matches the ISO specification, and add documentation > > http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php
2007-02-20Remove item:Bruce Momjian
< o ARRAY[[1,2],[3,4]])[1] should return the same values as < ARRAY[[1,2],[3,4]])[1:1]; <
2007-02-19Add FAQ text about Makefile.custom:Bruce Momjian
<P><I>src/Makefile.custom</I> can be used to set environment variables, like <I>CUSTOM_COPT</I>, that are used for every compile.
2007-02-19Update wording:Bruce Momjian
< * Consider allowing configuration of TOAST thresholds > * Allow user configuration of TOAST thresholds
2007-02-19Add:Bruce Momjian
> * Consider allowing configuration of TOAST thresholds > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php >
2007-02-19Add newlines.Bruce Momjian
2007-02-19Add:Bruce Momjian
> * Allow UPDATEs on only non-referential integrity columns not to conflict > with referential integrity locks > > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php
2007-02-19Add:Bruce Momjian
> * Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause > > http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php >
2007-02-19Done:Bruce Momjian
> * -Add ISO day of week format 'ID' to to_char() where Monday = 1
2007-02-19Done:Bruce Momjian
> * -Add a field 'isoyear' to extract(), based on the ISO week
2007-02-19Done:Bruce Momjian
< o Add long file support for binary pg_dump output < < While Win32 supports 64-bit files, the MinGW API does not, < meaning we have to build an fseeko replacement on top of the < Win32 API, and we have to make sure MinGW handles it. Another < option is to wait for the MinGW project to fix it, or use the < code from the LibGW32C project as a guide. < < http://archives.postgresql.org/pgsql-hackers/2006-12/msg00551.php < > o -Add long file support for binary pg_dump output
2007-02-18Update wording:Bruce Momjian
< Currently, ALTER USER and ALTER DATABASE support per-user and > Currently ALTER USER and ALTER DATABASE support per-user and < Currently, subtracting one date from another that crosses a > Currently subtracting one date from another that crosses a < Currently, SQL-language functions can only refer to parameters via $1, etc > Currently SQL-language functions can only refer to dollar parameters, > e.g. $1 < Currently, queries prepared via the libpq API are planned on first > Currently queries prepared via the libpq API are planned on first < Currently, SET <tab> causes a database lookup to check all > Currently SET <tab> causes a database lookup to check all < Currently, all statement results are transferred to the libpq > Currently all statement results are transferred to the libpq
2007-02-18Add:Bruce Momjian
* Allow SQL-language functions to reference parameters by parameter name Currently SQL-language functions can only refer to parameters via $1, etc
2007-02-17Add:Bruce Momjian
> * Allow holdable cursors in SPI
2007-02-17Add:Bruce Momjian
> > o Allow row and record variables to be set to NULL constants, > and allow NULL tests on such variables > > Because a row is not scalar, do not allow assignment > from NULL-valued scalars.
2007-02-16Add:Bruce Momjian
> o Consider reducing on-disk varlena length from four to two > because a heap row cannot be more than 64k in length
2007-02-14Add:Bruce Momjian
> > o Use LC_TIME for localized weekday/month names, rather than > LC_MESSAGES > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php
2007-02-14Add:Bruce Momjian
> * Clean up casting in /contrib/isn > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php >
2007-02-14Add:Bruce Momjian
> * Improve logging of prepared statements recovered during startup > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php >
2007-02-14Add URL for:Bruce Momjian
* Allow SQL-language functions to return results from RETURNING queries > > http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php >
2007-02-14Add URL for:Bruce Momjian
> > http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php >
2007-02-13Add URL for:Bruce Momjian
* Update Bonjour to work with newer cross-platform SDK > http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php
2007-02-13Add:Bruce Momjian
> * Improve failure message when DROP DATABASE is used on a database that > has prepared transactions
2007-02-13Add URL for:Bruce Momjian
* Update Bonjour to work with newer cross-platform SDK > > http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php >
2007-02-13Add:Bruce Momjian
> * Update our code to handle 64-bit timezone files to match the zic > source code, which now uses them
2007-02-09Update FAQ for new 24-byte header, down from 28.Bruce Momjian
2007-02-09Add blank line.Bruce Momjian
2007-02-09Add URL for:Bruce Momjian
< > http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php
2007-02-09Done!Bruce Momjian
< * Merge xmin/xmax/cmin/cmax back into three header fields < < Before subtransactions, there used to be only three fields needed to < store these four values. This was possible because only the current < transaction looks at the cmin/cmax values. If the current transaction < created and expired the row the fields stored where xmin (same as < xmax), cmin, cmax, and if the transaction was expiring a row from a < another transaction, the fields stored were xmin (cmin was not < needed), xmax, and cmax. Such a system worked because a transaction < could only see rows from another completed transaction. However, < subtransactions can see rows from outer transactions, and once the < subtransaction completes, the outer transaction continues, requiring < the storage of all four fields. With subtransactions, an outer < transaction can create a row, a subtransaction expire it, and when the < subtransaction completes, the outer transaction still has to have < proper visibility of the row's cmin, for example, for cursors. < < One possible solution is to create a phantom cid which represents a < cmin/cmax pair and is stored in local memory. Another idea is to < store both cmin and cmax only in local memory. < > * -Merge xmin/xmax/cmin/cmax back into three header fields
2007-02-09Update:Bruce Momjian
< * Consider placing all sequences in a single table > * Consider placing all sequences in a single table, or create a system > view
2007-02-09Update:Bruce Momjian
< * Consider placing all sequences in a single table, now that system < tables are full transactional > * Consider placing all sequences in a single table
2007-02-09Add:Bruce Momjian
> * Consider placing all sequences in a single table, now that system > tables are full transactional
2007-02-08Add URL for:Bruce Momjian
* Add support for SQL-standard GENERATED/IDENTITY columns > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php
2007-02-07Update for 8.2.3.Bruce Momjian
2007-02-06Update for 8.2.2 as most recent release.Bruce Momjian
2007-02-06Update workding for daylight savings time.Bruce Momjian
2007-02-06Update timezone FAQ item:Bruce Momjian
<P>USA saving time changes are included in PostgreSQL release 8.0.[4+], and all later major releases, e.g. 8.1. Canada and Western Australia changes are included in 8.0.[10+], 8.1.[6+], and all later major releases. PostgreSQL releases prior to 8.0 use the operating system's timezone database for daylight saving information.</P>
2007-02-06Split apart entries, one done now:Bruce Momjian
* -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h * Consider making NAMEDATALEN more configurable in future releases
2007-02-05Updated TODO item:Bruce Momjian
> o Add a \set variable to control whether \s displays line numbers > Another option is to add \# which lists line numbers, and > allows command execution. > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
2007-02-05Modify:Bruce Momjian
< o Add \# to list command history like \s, but with line numbers > o Add \# to list and execute command history
2007-02-04Add:Bruce Momjian
> > * Allow custom variable classes that can restrict who can set the values > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php >
2007-02-04Update URL for:Bruce Momjian
* Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning"
2007-02-04Add:Bruce Momjian
> > o Add \# to list command history like \s, but with line numbers > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php >
2007-02-03Add URLs for:Bruce Momjian
* Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning" > http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php
2007-02-03Add:Bruce Momjian
> o Allow recovery.conf to allow the same syntax as > postgresql.conf, including quoting > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
2007-02-03Add patches thread for:Bruce Momjian
* Reduce checkpoint performance degredation by forcing data to disk more evenly > http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php
2007-02-02Add URL for:Bruce Momjian
* Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning" > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php
2007-02-02Add:Bruce Momjian
> * Reduce checkpoint performance degredation by forcing data to disk > more evenly > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php
2007-02-02Add URL for:Bruce Momjian
o Fix RENAME to work on variables other than OLD/NEW > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php
generated by cgit v1.2.3 (git 2.46.0) at 2025-10-02 19:02:48 +0000