Age | Commit message (Collapse) | Author |
|
< recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php.
> recovery.
> http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php
< Right now only one encoding is allowed per database. For a partial
< patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php.
> Right now only one encoding is allowed per database.
> http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php
459c460
< notify the protocol when a RESET CONNECTION command is used. See
> notify the protocol when a RESET CONNECTION command is used.
461d461
< for a partial implementation.
515c515
< See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php.
> http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php
535c535
< See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php.
> http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php
821c821
< See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php.
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php
877c877
< Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php.
> http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php
< See partially completed patch and additional work required at
< http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php.
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php
1297c1296
< See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php.
> http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php
1311c1310,1311
< o Improve signal handling,
> o Improve signal handling
>
1312a1313
>
|
|
< * Support triggers on columns (Greg Sabino Mullane)
> * Support triggers on columns
>
> See http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php.
>
|
|
Robert Treat
|
|
> * -Allow server logs to be remotely read and removed using SQL commands
|
|
>
> See http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php.
>
|
|
< recovery.
> recovery. See http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php.
|
|
< Right now only one encoding is allowed per database.
> Right now only one encoding is allowed per database. For a partial
> patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php.
|
|
< * Add SQL99 WITH RECURSIVE to SELECT
> * Add SQL99 WITH RECURSIVE (hierarchical) queries to SELECT
|
|
> * Consider allowing control of upper/lower case folding of unquoted
> identifiers
>
> Details at http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php.
|
|
< o Allow timezone names in SQL strings, '2006-05-24 21:11
> o -Allow timezone names in SQL strings, '2006-05-24 21:11
|
|
Robert Treat
|
|
>
> Particularly, move GPL-licensed /contrib/userlock and
> /contrib/dbmirror/clean_pending.pl.
>
|
|
that the Mackert-Lohmann formula applies across all the repetitions of the
nestloop, not just each scan independently. We use the M-L formula to
estimate the number of pages fetched from the index as well as from the table;
that isn't what it was designed for, but it seems reasonably applicable
anyway. This makes large numbers of repetitions look much cheaper than
before, which accords with many reports we've received of overestimation
of the cost of a nestloop. Also, change the index access cost model to
charge random_page_cost per index leaf page touched, while explicitly
not counting anything for access to metapage or upper tree pages. This
may all need tweaking after we get some field experience, but in simple
tests it seems to be giving saner results than before. The main thing
is to get the infrastructure in place to let cost_index() and amcostestimate
functions take repeated scans into account at all. Per my recent proposal.
Note: this patch changes pg_proc.h, but I did not force initdb because
the changes are basically cosmetic --- the system does not look into
pg_proc to decide how to call an index amcostestimate function, and
there's no way to call such a function from SQL at all.
|
|
< notify the protocol when a RESET CONNECTION command is used.
> notify the protocol when a RESET CONNECTION command is used. See
> http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
> for a partial implementation.
|
|
< * %Make postmater and postgres options distinct so the postmaster -o
> * -Make postmater and postgres options distinct so the postmaster -o
|
|
This shouldn't affect simple indexscans much, while for bitmap scans that
are touching a lot of index rows, this seems to bring the estimates more
in line with reality. Per recent discussion.
|
|
assumed that a sequential page fetch has cost 1.0. This patch doesn't
in itself change the system's behavior at all, but it opens the door to
people adopting other units of measurement for EXPLAIN costs. Also, if
we ever decide it's worth inventing per-tablespace access cost settings,
this change provides a workable intellectual framework for that.
|
|
< * %Remove behavior of postmaster -o
> * %Make postmater and postgres options distinct so the postmaster -o
> option is no longer needed
|
|
< o Allow COPY to output from views
> o Allow COPY to output from SELECT
570c570
< Another idea would be to allow actual SELECT statements in a COPY.
> COPY should also be able to output views.
|
|
Robert Treat
|
|
Robert Treat
|
|
> * Allow WAL information to recover corrupted pg_controldata
>
> See partially completed patch and additional work required at
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php.
>
|
|
Per Larry Rosenman.
|
|
> * Allow WAL information to recover corrupted pg_controldata
|
|
http://archives.postgresql.org/pgsql-hackers/2006-05/msg00002.php
|
|
|
|
the server. Per discussion, there seems no point in a waiting period
before making this required.
|
|
|
|
|
|
as this seems only likely to create headaches for module developers. Put
the macro in the pre-existing fmgr.h file instead. Avoid being too cute
about how many fields we can cram into a word, and avoid trying to fetch
from a library we've already unlinked.
Along the way, it occurred to me that the magic block really ought to be
'const' so it can be stored in the program text area. Do the same for
the existing data blocks for PG_FUNCTION_INFO_V1 functions.
|
|
It now only checks four things:
Major version number (7.4 or 8.1 for example)
NAMEDATALEN
FUNC_MAX_ARGS
INDEX_MAX_KEYS
The three constants were chosen because:
1. We document them in the config page in the docs
2. We mark them as changable in pg_config_manual.h
3. Changing any of these will break some of the more popular modules:
FUNC_MAX_ARGS changes fmgr interface, every module uses this NAMEDATALEN
changes syscache interface, every PL as well as tsearch uses this
INDEX_MAX_KEYS breaks tsearch and anything using GiST.
Martijn van Oosterhout
|
|
---------------------------------------------------------------------------
Add dynamic record inspection to PL/PgSQL, useful for generic triggers:
tval2 := r.(cname);
or
columns := r.(*);
Titus von Boxberg
|
|
tval2 := r.(cname);
or
columns := r.(*);
Titus von Boxberg
|
|
|
|
Joachim Wieland
|
|
An article at WebProNews quoted from the PG docs as to the merits of
stored procedures. I have added a bit more material on their merits,
as well as making a few changes to improve the introductions to
PL/Perl and PL/Tcl.
Chris Browne
|
|
J.Kuwamura
|
|
> * Consider GnuTLS if OpenSSL license becomes a problem
>
> See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php.
|
|
> o Allow timezone names in SQL strings, '2006-05-24 21:11
> Americas/New_York'::timestamptz
|
|
with a fresh local value for each invocation, to avoid unexpected sharing
violations. Per recent -hackers discussion.
|
|
|
|
in place though, so that it plays nicely with older servers.
Per discussion.
|
|
|
|
during COPY OUT. Andreas Pflug, some editorialization by moi.
|
|
regression test.
|
|
kept but now deprecated. Patch from Adam Sjøgren. Add regression test to
show plperl trigger data (Andrew).
TBD: apply similar changes to plpgsql, plpython and pltcl.
|
|
< pg_attribute.attislocal has to be set to 'false' for ADD, and
< pg_attribute.attinhcount adjusted appropriately
> See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php.
|
|
* some refactoring and simplify code int gistutil.c and gist.c
* now in some cases it can be called used-defined
picksplit method for non-first column in index, but here
is a place to do more.
* small fix of docs related to support NULL.
|
|
the thread-safety status of the library.
|
|
> This allows tables to be added/removed from an inheritance
> hierarchy. This is particularly useful for table partitioning.
|