| Age | Commit message (Collapse) | Author |
|
and bogus documentation (dimension arrays are int[] not anyarray). Also the
errhint() messages seem to be really errdetail(), since there is nothing
heuristic about them. Some other trivial cosmetic improvements.
|
|
to acquire shared table locks within a specified amount of time.
David Gould
|
|
ITAGAKI Takahiro
|
|
(Unlike the original submission, this patch treats TABLE output parameters
as being entirely equivalent to OUT parameters -- tgl)
Pavel Stehule
|
|
* Implement SQL:2003 window functions
> http://archives.postgresql.org/pgsql-hackers/2008-07/msg00232.php
|
|
>
> * Reduce locking requirements for creating a trigger
>
> http://archives.postgresql.org/pgsql-hackers/2008-06/msg00635.php
>
|
|
* Implement SQL:2003 window functions
>
> http://archives.postgresql.org/pgsql-hackers/2008-06/msg00380.php
>
|
|
need to deconstruct proargmodes for each pg_proc entry inspected by
FuncnameGetCandidates(). Fixes function lookup performance regression
caused by yesterday's variadic-functions patch.
In passing, make pg_proc.probin be NULL, rather than a dummy value '-',
in cases where it is not actually used for the particular type of function.
This should buy back some of the space cost of the extra column.
|
|
>
> o Add external tool to auto-tune some postgresql.conf parameters
>
> http://archives.postgresql.org/pgsql-hackers/2008-06/msg00000.php
>
|
|
so long as all the trailing arguments are of the same (non-array) type.
The function receives them as a single array argument (which is why they
have to all be the same type).
It might be useful to extend this facility to aggregates, but this patch
doesn't do that.
This patch imposes a noticeable slowdown on function lookup --- a follow-on
patch will fix that by adding a redundant column to pg_proc.
Pavel Stehule
|
|
Pavel Stehule
|
|
|
|
|
|
>
> o Reduce PITR WAL file size by removing full page writes and
> by removing trailing bytes to improve compression
|
|
>
> * Consider decreasing the I/O caused by updating tuple hint bits
>
> http://archives.postgresql.org/pgsql-hackers/2008-05/msg00847.php
>
|
|
> o -Have psql show current values for a sequence
|
|
Report from Martin Saschek
|
|
> * Improve ability to modify views via ALTER TABLE
>
> http://archives.postgresql.org/pgsql-hackers/2008-05/msg00691.php
|
|
< * Add temporal versions of generate_series()
> * -Add temporal versions of generate_series()
|
|
* Consider allowing control of upper/lower case folding of unquoted
identifiers
> http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php
|
|
< o Fix server restart problem when the server was shutdown during
> o -Fix server restart problem when the server was shutdown during
|
|
on the most common individual lexemes in place of the mostly-useless default
behavior of counting duplicate tsvectors. Future work: create selectivity
estimation functions that actually do something with these stats.
(Some other things we ought to look at doing: using the Lossy Counting
algorithm in compute_minimal_stats, and using the element-counting idea for
stats on regular arrays.)
Jan Urbanski
|
|
|
|
|
|
Document return type of cast functions.
Also change documentation to prefer the term "binary coercible" in its
present sense instead of the previous term "binary compatible".
|
|
wal_segment_size to make those configuration parameters available to clients,
in the same way that block_size was previously exposed. Bernd Helmle, with
comments from Abhijit Menon-Sen and some further tweaking by me.
|
|
|
|
known to the SQL parser. Dave Page
|
|
|
|
Guillaume Lelarge, with some additional fixes by me.
|
|
which are available if LOCK_DEBUG is defined.
|
|
* Add database and transaction-level triggers
|
|
> * Fix TRUNCATE ... RESTART IDENTITY so its affect on sequences is rolled
> back on transaction abort
|
|
> o Add "auto" expanded mode that outputs in expanded format if
> "wrapped" mode can't wrap the output to the screen width
>
> http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php
>
|
|
> o Add option to wrap column values at whitespace boundaries,
> rather than chopping them at a fixed width.
> Currently, "wrapped" format chops values into fixed
> widths. Perhaps the word wrapping could use the same
> algorithm documented in the W3C specification.
> http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php
> http://www.w3.org/TR/CSS21/tables.html#auto-table-layout
|
|
As the buffer could now be a lot larger than before, and copying it could
thus be a lot more expensive than before, use strcpy instead of memcpy to
copy the query string, as was already suggested in comments. Also, only copy
the PgBackendStatus struct and string if the slot is in use.
Patch by Thomas Lee, with some changes by me.
|
|
values to libpq.
|
|
>
> * Fix system views like pg_stat_all_tables to use set-returning
> functions, rather than views of per-column functions
|
|
truly distinct version of IF. Per suggestion from Marko Kreen.
|
|
appear in a paragraph.
Andy Anderson
|
|
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg01890.php
|
|
* Improve server security options
http://archives.postgresql.org/pgsql-hackers/2008-04/msg01875.php
http://archives.postgresql.org/pgsql-hackers/2008-05/msg00000.php
|
|
|
|
|
|
>
> * Improve LDAP authentication configuration options
>
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg01745.php
|
|
|
|
< o Prevent pg_dump/pg_restore from being affected by
> o -Prevent pg_dump/pg_restore from being affected by
|
|
>
> o Allow COPY to report errors sooner
>
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg01169.php
|
|
|
|
Joshua D. Drake
|