| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
| |
> * Allow WAL information to recover corrupted pg_controldata
|
| |
|
| |
|
| |
|
|
|
|
| |
> * Allow pg_dump to dump sequences using NO_MAXVALUE and NO_MINVALUE
|
| |
|
|
|
|
|
|
| |
known problem with failure to respond to 'pg_ctl stop -m fast', and
probable problems if SIGINT or SIGTERM arrives while processing a
SIGUSR2 interrupt that arrived while waiting for a new client query.
|
|
|
|
| |
> * Add a script to ask system configuration questions and tune postgresql.conf
|
|
|
|
| |
consistency.
|
|
|
|
| |
> * Allow CIDR format to be used in pg_hba.conf
|
|
|
|
|
|
|
|
|
|
|
| |
< o Allow CLUSTER to cluster all tables (Alvaro Herrera)
> o -Allow CLUSTER to cluster all tables (Alvaro Herrera)
243c243
< * Allow pg_dump to dump a specific schema (Neil Conway)
> * -Allow pg_dump to dump a specific schema (Neil Conway)
398c398
< * Make IN/NOT IN have similar performance to EXISTS/NOT EXISTS (Tom)
> * -Make IN/NOT IN have similar performance to EXISTS/NOT EXISTS (Tom)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
> o -Add ALTER TABLE tab SET WITHOUT OIDS (Rod)
> o -Allow CLUSTER to cluster all tables (Alvaro Herrera)
> * -Allow pg_dump to dump a specific schema (Neil Conway)
> * -Make IN/NOT IN have similar performance to EXISTS/NOT EXISTS (Tom)
> * Rod is Rod Taylor <pg@rbt.ca)>
|
|
|
|
|
| |
< * -Make a transaction-safe TRUNCATE
> * -Make a transaction-safe TRUNCATE (Rod)
|
|
|
|
| |
> * -Make a transaction-safe TRUNCATE
|
| |
|
|
|
|
|
|
|
| |
in the case where the node immediately above the scan is a Hash, Sort,
or Material node. In these cases it's better to do the projection
so that we don't store unneeded columns in the hash/sort/materialize
table. Per discussion a few days ago with Anagh Lal.
|
|
|
|
|
| |
that turn into CASE expressions. They evaluate their arguments at most
once. Patch by Kris Jurka, review and (very light) editorializing by me.
|
|
|
|
|
| |
< * Disallow DROP COLUMN on a column that is part of a multi-column index
> * Require DROP COLUMN CASCADE for a column that is part of a multi-column index
|
|
|
|
| |
a bad choice between sorted and hashed aggregation.
|
|
|
|
|
|
|
|
|
| |
the outer query. (The implementation is a bit klugy, but it would take
nontrivial restructuring to make it nicer, which this is probably not
worth.) This avoids unnecessary sort steps in examples like
SELECT foo,count(*) FROM (SELECT ... ORDER BY foo,bar) sub GROUP BY foo
which means there is now a reasonable technique for controlling the
order of inputs to custom aggregates, even in the grouping case.
|
|
|
|
| |
> * Disallow DROP COLUMN on a column that is part of a multi-column index
|
|
|
|
| |
ps for multiple postmasters, for Kevin Brown.
|
|
|
|
| |
same type in a rule. Per bug report from Pavel Hanak.
|
| |
|
|
|
|
| |
> * Allow incremental backups
|
| |
|
|
|
|
| |
> * Add schema option to createlang
|
|
|
|
| |
Change was actually made in a previous commit.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
- More work on Informix compatibility.
|
|
|
|
| |
> * Cache last known per-tuple offsets to speed long tuple access
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
SIGPIPE disabled, and does not need to waste two syscalls per I/O on it.
|
| |
|
| |
|
|
|
|
| |
an ALTER TABLE ADD COLUMN command. Per bug #896.
|
|
|
|
|
| |
the table(s) modified by the original query would get checked for the
type of write permission needed by a rule query.
|
|
|
|
|
|
|
|
| |
of the containing query (which really can only happen in a rule context).
Per example from Brandon Craig Rhodes. Also, make the error message
more specific for the similar case with sub-select in FROM. The revised
coding should be easier to adapt to SQL99's LATERAL(), when we get around
to supporting that.
|
| |
|
|
|
|
|
|
|
| |
from Greg Stark. Also, twiddle the FuncCall case to not scribble on
the input structure, which was the proximate cause of the problem.
Someday we ought to fix things so that transformExpr() isn't called
on already-transformed trees ...
|
| |
|