| Age | Commit message (Collapse) | Author |
|---|
|
* 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
|
|
> * Allow custom variables to appear in pg_settings()
|
|
* Implement a module capability for loading /contrib-style extensions
http://archives.postgresql.org/pgsql-patches/2008-04/msg00164.php
|
|
binary values.
Add comments to libpq C function for parameter passing.
|
|
* Consider whether duplicate keys should be sorted by block/offset
http://archives.postgresql.org/pgsql-hackers/2008-03/msg00558.php
Create new "Sorting" TODO section.
|
|
o Allow pg_hba.conf to specify host names along with IP addresses
> http://archives.postgresql.org/pgsql-hackers/2008-06/msg00569.php
|
|
along with an additional typo I noticed along the way.
|
|
late, with lots of redundancy, bad grammar, and just plain poor exposition.
Make it clear that autovacuum is now considered the normal solution.
|
|
grammar allows ALTER TABLE/INDEX/SEQUENCE/VIEW interchangeably for all
subforms of those commands, and then we sort out what's really legal
at execution time. This allows the ALTER SEQUENCE/VIEW reference pages
to fully document all the ALTER forms available for sequences and views
respectively, and eliminates a longstanding cause of confusion for users.
The net effect is that the following forms are allowed that weren't before:
ALTER SEQUENCE OWNER TO
ALTER VIEW ALTER COLUMN SET/DROP DEFAULT
ALTER VIEW OWNER TO
ALTER VIEW SET SCHEMA
(There's no actual functionality gain here, but formerly you had to say
ALTER TABLE instead.)
Interestingly, the grammar tables actually get smaller, probably because
there are fewer special cases to keep track of.
I did not disallow using ALTER TABLE for these operations. Perhaps we
should, but there's a backwards-compatibility issue if we do; in fact
it would break existing pg_dump scripts. I did however tighten up
ALTER SEQUENCE and ALTER VIEW to reject non-sequences and non-views
in the new cases as well as a couple of cases where they didn't before.
The patch doesn't change pg_dump to use the new syntaxes, either.
|
|
expand the pattern specifier.
Per gripe from Josh Drake.
|
|
> o Add functions to syntax check configuration files
>
< * Add pg_ctl option to do a syntax check of postgresql.conf
|
|
|
|
< * Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause
> * Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause or
> target list
> http://archives.postgresql.org/pgsql-hackers/2008-06/msg00124.php
|
|
> * Add pg_ctl option to do a syntax check of postgresql.conf
|
|
David Fetter.
|
|
|
|
Jun Kuwamura
|
|
|
|
|
|
|
