| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
| |
> o -SELECT col FROM tab WHERE numeric_col = 10.1 fails, requires quotes
|
| |
|
|
|
|
|
|
| |
available (else there's no way to interpret the list links). Change
pg_locks view to show transaction ID locks separately from ordinary
relation locks. Avoid showing N duplicate rows when the same lock is
held multiple times (seems unlikely that users care about exact hold
count). Improve documentation.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
to false provides more SQL-spec-compliant behavior than we had before.
I am not sure that setting it false is actually a good idea yet; there
is a lot of client-side code that will probably be broken by turning
autocommit off. But it's a start.
Loosely based on a patch by David Van Wie.
|
| |
|
|
|
|
| |
column additions, deletions, and renames that would let a child table
get out of sync with its parent. Patch by Alvaro Herrera, with some
kibitzing by Tom Lane.
|
| | |
|
| | |
|
| |
|
|
|
| |
* Remove wal_files postgresql.conf option because WAL files are
now recycled
|
| |
|
|
| |
Improve wording of pre-7.3 syntax mention.
|
| | |
|
| |
|
|
|
| |
that the functionality is available to anyone via ReturnSetInfo, rather
than hard-wiring it to PL/pgSQL.
|
| |
|
|
| |
translation.
|
| |
|
|
| |
Manfred Koizar
|
| |
|
|
|
|
|
| |
to the table function, thus preventing memory leakage accumulation across
calls. This means that SRFs need to be careful to distinguish permanent
and local storage; adjust code and documentation accordingly. Patch by
Joe Conway, very minor tweaks by Tom Lane.
|
| | |
|
| |
|
|
|
| |
INSERT, UPDATE, or DELETE shouldn't change FOUND. IMHO anyway.
Also, try to make documentation a little clearer.
|
| |
|
|
| |
This breaks support for 6.2 or older client libraries.
|
| |
|
|
|
| |
types, SRFs. Not happy with memory management yet, but I'll commit these
other changes.
|
| |
|
|
|
|
| |
Note can probably be removed after a couple of releases.
Rod Taylor
|
| |
|
|
| |
< * Remove PGPASSWORD because it is insecure on some OS's, in 7.4
|
| | |
|
| |
|
|
| |
a more logical ordering.
|
| |
|
|
| |
> o Add SET SCHEMA
|
| |
|
|
|
|
| |
formatting (\timing) works correctly. Change "Total time" to "Time"
since there is nothing that "total" refers to. Remove non-multibyte
code.
|
| |
|
|
| |
except that it's more robust, reconnects less often, and is NLS'ed.
|
| |
|
|
| |
> * Allow free space map to be auto-sized or warn when it is too small
|
| | |
|
| |
|
|
|
| |
> * Allow REINDEX to rebuild all indexes, remove /contrib/reindex
> o Allow CLUSTER to cluster all tables, remove clusterdb
|
| |
|
|
| |
from Tom Lane.
|
| |
|
|
| |
> o -Cluster all tables at once using pg_index.indisclustered set during
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bit on the indexes.
I also attach clusterdb and clusterdb.sgml; both of them are blatant
rips of vacuumdb and vacuumdb.sgml, but get the job done. Please review
them, as I'm probably making a lot of mistakes with SGML and I can't
compile it here.
vacuumdb itself is not very comfortable to use when the databases have
passwords, because it has to connect once for each table (I can probably
make it connect only once for each database; should I?). Because of
this I added a mention of PGPASSWORDFILE in the documentation, but I
don't know if that is the correct place for that.
Alvaro Herrera
|
| | |
|
| | |
|
| |
|
|
| |
> partial page writes [wal]
|
| |
|
|
| |
> * Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
|
| |
|
|
| |
< o Add plsh server-side shell language (Peter E)
|
| | |
|
| | |
|
| |
|
|
| |
> * Allow DELETE to handle table aliases for self-joins [delete]
|
| | |
|
| | |
|
| |
|
|
| |
> * Allow triggers to be disabled [trigger]
|
| | |
|
| | |
|
| |
|
|
| |
> * Return proper effected tuple count from complex commands [return]
|
| | |
|
| | |
|
