| Commit message (Collapse) | Author | Age |
|
|
|
| |
it now lives (per discussion). Leave the other FAQs alone for now.
|
|
|
|
| |
Update FAQs for 8.2.5.
|
|
|
|
| |
8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19.
|
| |
|
|
|
|
| |
Jun Kuwamura
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At any rate, here's a revision to CVS HEAD to reflect some changes by
myself and by Seneca Cunningham for the AIX FAQ. It touches on the
following issues:
1. memcpy pointer patch for dynahash.c
2. AIX memory management, which can, for 32 bit cases, bite people
quite unexpectedly...
Chris Browne
|
|
|
|
| |
J.Kuwamura
|
|
|
|
| |
J.Kuwamura
|
|
|
|
| |
Victor Vislobokov
|
|
|
|
| |
Backpatch FAQ's to 8.1.X.
|
| |
|
|
|
|
| |
Robert Treat
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
J.Kuwamura
|
| |
|
|
|
|
|
| |
< o Allow ALTER TABLE RENAME CONSTRAINT
> o Add ALTER TABLE RENAME CONSTRAINT, update index name also
|
|
|
|
|
| |
> o Have ALTER INDEX update the name of a constraint using that index
> o Allow ALTER TABLE RENAME CONSTRAINT
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
< o Add a GUC variable to allow output of interval values in ISO8601
< format
212a211,223
> o Add a GUC variable to allow output of interval values in ISO8601
> format
> o Improve timestamptz subtraction to be DST-aware
>
> Currently, subtracting one date from another that crosses a
> daylight savings time adjustment can return '1 day 1 hour', but
> adding that back to the first date returns a time one hour in
> the future. This is caused by the adjustment of '25 hours' to
> '1 day 1 hour', and '1 day' is the same time the next day, even
> if daylight savings adjustments are involved.
>
> o Fix interval display to support values exceeding 2^31 hours
> o Add overflow checking to timestamp and interval arithmetic
|
|
|
|
|
|
|
|
| |
>
> o Add auto-expanded mode so expanded output is used if the row
> length is wider than the screen width.
>
> Consider using auto-expanded mode for backslash commands like \df+.
|
|
|
|
|
| |
> * Allow user-defined functions retuning a domain value to enforce domain
> constraints
|
|
|
|
|
|
|
|
| |
> * Prevent PQfnumber() from lowercasing unquoted the column name
>
> PQfnumber() should never have been doing lowercasing, but historically
> it has so we need a way to prevent it
>
|
|
|
|
|
|
|
|
| |
< * Prevent libpq's PQfnumber() from lowercasing the column name
<
< One idea is to lowercase all identifiers except those that are
< surrounded by quotes.
<
|
|
|
|
|
|
|
|
|
|
|
| |
<
< * Add code to detect an SMP machine and handle spinlocks accordingly
< from distributted.net, http://www1.distributed.net/source,
< in client/common/cpucheck.cpp
<
< On SMP machines, it is possible that locks might be released shortly,
< while on non-SMP machines, the backend should sleep so the process
< holding the lock can complete and release it.
|
|
|
|
|
|
|
|
|
| |
< o %Add dumping of comments on composite type columns
< o %Add dumping of comments on index columns
< o Stop dumping CASCADE on DROP TYPE commands in clean mode
> o %Add dumping of comments on index columns and composite type columns
604a603
> o Stop dumping CASCADE on DROP TYPE commands in clean mode
|
|
|
|
|
|
|
| |
< o %Replace crude DELETE FROM method of pg_dumpall --clean for
< cleaning of roles with separate DROP commands
608a607
>
|
|
|
|
|
|
| |
<
> o Allow pg_dump --clean to drop roles that own objects or have
> privileges
|
|
|
|
|
|
|
|
|
| |
< * Prevent libpq's PQfnumber() from lowercasing the column name?
> * Prevent libpq's PQfnumber() from lowercasing the column name
>
> One idea is to lowercase all identifiers except those that are
> surrounded by quotes.
>
|
|
|
|
| |
> o Add options like pg_restore -l and -L to pg_dump
|
|
|
|
|
|
|
| |
> o Allow selection of individual object(s) of all types, not just
> tables
> o In a selective dump, allow dumping of an object and all its
> dependencies
|
|
|
|
|
|
|
|
| |
< * Consider compressing indexes by storing key prefix values shared by
> * Consider compressing indexes by storing key values duplicated in
735a736,737
>
> This is difficult because it requires datatype-specific knowledge.
|
|
|
|
|
|
| |
<
> * Consider compressing indexes by storing key prefix values shared by
> several rows as a single index entry
|
|
|
|
| |
Jun Kuwamura
|
| |
|
|
|
|
| |
< * -Have sequence dependency track use of DEFAULT sequences
|
|
|
|
|
|
| |
< * Have sequence dependency track use of DEFAULT sequences,
< seqname.nextval?
> * -Have sequence dependency track use of DEFAULT sequences
|
| |
|
|
|
|
| |
Victor Vislobokov
|
|
|
|
|
| |
< * +Add options to pg_config to show the share_dir, sysconfdir,
< pkgincludedir, and localedir
|
|
|
|
|
| |
> o Improve signal handling,
> http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php
|