| Age | Commit message (Collapse) | Author |
|---|
|
the DROP pass rather than the ADD_CONSTR pass. On examining the code I
think this was just an oversight rather than intentional, and it seems
to satisfy the principle of least surprise better than the alternative
solution that was discussed. Add an example to the ref page showing how
to do ALTER TYPE and update the default in one command. Per gripe from
Markus Bertheau that that wasn't possible.
|
|
as grantees, not PUBLIC ... and you can't say GROUP either. Noted by
Brian Hurt.
|
|
< o Add COPY TO STDIN / STDOUT handling
> o Add COPY TO STDIN handling
|
|
> o In rules, allow VALUES() to contain a mixture of 'old' and 'new'
> references
|
|
o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)
|
|
of the text where appropiate.
|
|
if table creation failed (the table already exists).
Martin Pitt
|
|
< o %Allow pg_dump to use multiple -t and -n switches [pg_dump]
<
< http://archives.postgresql.org/pgsql-patches/2006-01/msg00190.php
<
> o -Allow pg_dump to use multiple -t and -n switches, exclusion
> ability, and regular expression object matching
|
|
and -N options to exclude objects. Also support regular expressions for
option object names.
Greg Sabino Mullane
|
|
Joshua D. Drake
Robert Treat
|
|
> * Consider compressed annealing to search for query plans
>
> This might replace GEQO, http://sixdemonbag.org/Djinni.
|
|
(table or index) before trying to open its relcache entry. This fixes
race conditions in which someone else commits a change to the relation's
catalog entries while we are in process of doing relcache load. Problems
of that ilk have been reported sporadically for years, but it was not
really practical to fix until recently --- for instance, the recent
addition of WAL-log support for in-place updates helped.
Along the way, remove pg_am.amconcurrent: all AMs are now expected to support
concurrent update.
|
|
created in the bootstrap phase proper, rather than added after-the-fact
by initdb. This is cleaner than before because it allows us to retire the
undocumented ALTER TABLE ... CREATE TOAST TABLE command, but the real reason
I'm doing it is so that toast tables of shared catalogs will now have
predetermined OIDs. This will allow a reasonably clean solution to the
problem of locking tables before we load their relcache entries, to appear
in a forthcoming patch.
|
|
|
|
> * Consider detoasting keys before sorting
|
|
> * Add column to pg_stat_activity that shows the progress of long-running
> commands like CREATE INDEX and VACUUM
|
|
> * Add support for SQL-standard GENERATED/IDENTITY columns
>
> http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php
|
|
> * Allow DISTINCT to work in multiple-argument aggregate calls
< o Allow UPDATE to handle complex aggregates [update]?
|
|
the float8 versions of the aggregates, which is all that the standard requires.
Sergey's original patch also provided versions using numeric arithmetic,
but given the size and slowness of the code, I doubt we ought to include
those in core.
|
|
|
|
server-side character set.
|
|
< * Tatsuo is Tatsuo Ishii <t-ishii@sra.co.jp> of Software Research Assoc.
> * Tatsuo is Tatsuo Ishii <ishii@sraoss.co.jp> of SRA OSS, Inc. Japan
|
|
|
|
>
> A subselect can also be used as the value source.
|
|
the opportunity to treat COUNT(*) as a zero-argument aggregate instead
of the old hack that equated it to COUNT(1); this is materially cleaner
(no more weird ANYOID cases) and ought to be at least a tiny bit faster.
Original patch by Sergey Koposov; review, documentation, simple regression
tests, pg_dump and psql support by moi.
|
|
Albe Laurenz
|
|
|
|
< o Allow point-in-time recovery to archive partially filled
< write-ahead logs? [pitr]
> o Add command to archive partially filled write-ahead logs? [pitr]
< of a disk failure. This could be triggered by a user command or
< a timer.
> of a disk failure.
< recovery. A function call to do this would also be useful.
> recovery.
> o Add reporting of the current WAL file and offset, perhaps as
> part of partial log file archiving
>
> The offset allows parts of a WAL file to be archived using
> an external program.
>
< o Add reporting of the current WAL file and offset, perhaps as
< part of partial log file archiving
<
< The offset allows parts of a WAL file to be archived using
< an external program.
|
|
upcoming units feature.
|
|
> * -Change LIMIT/OFFSET and FETCH/MOVE to use int8
|
|
>
> The offset allows parts of a WAL file to be archived using
> an external program.
|
|
< o Add reporting of the current WAL file, perhaps as part of
< partial log file archiving
> o Add reporting of the current WAL file and offset, perhaps as
> part of partial log file archiving
|
|
< write-ahead logs [pitr]
> write-ahead logs? [pitr]
< recovery.
> recovery. A function call to do this would also be useful.
|
|
> o -Allow customization of the known set of TZ names (generalize the
|
|
configuration files that can be altered by a DBA. The australian_timezones
GUC setting disappears, replaced by a timezone_abbreviations setting (set this
to 'Australia' to get the effect of australian_timezones). The list of zone
names defined by default has undergone a bit of cleanup, too. Documentation
still needs some work --- in particular, should we fix Table B-4, or just get
rid of it? Joachim Wieland, with some editorializing by moi.
|
|
by Robert Lor
|
|
|
|
|
|
just exec instead of creating a subprocess. This reduces process usage
from four processes per parallel test to two. I have no idea whether
a comparable optimization is possible or useful in the Windows port.
|
|
This allows it to be used on Windows without installing mingw
(though you do still need 'diff'), and opens the door to future
improvements such as message localization.
Magnus Hagander and Tom Lane.
|
|
o -Display IN, INOUT, and OUT parameters in \df
|
|
don't include a space between the function name and the parenthesis
that begins its parameter list, for consistency.
|
|
|
|
are alphabetically ordered. I believe the tables were correctly ordered in
the past, but some of them had subsequently regressed.
|
|
|
|
it can handle small fillfactors for ordinary-sized index entries without
failing on large ones; fix nbtinsert.c to distinguish leaf and nonleaf
pages; change the minimum fillfactor to 10% for all index types.
|
|
SGML cleanup: sort table entries alphabetically.
|
|
|
|
|
|
To this end, add a couple of columns to pg_class, relminxid and relvacuumxid,
based on which we calculate the pg_database columns after each vacuum.
We now force all databases to be vacuumed, even template ones. A backend
noticing too old a database (meaning pg_database.datminxid is in danger of
falling behind Xid wraparound) will signal the postmaster, which in turn will
start an autovacuum iteration to process the offending database. In principle
this is only there to cope with frozen (non-connectable) databases without
forcing users to set them to connectable, but it could force regular user
database to go through a database-wide vacuum at any time. Maybe we should
warn users about this somehow. Of course the real solution will be to use
autovacuum all the time ;-)
There are some additional improvements we could have in this area: for example
the vacuum code could be smarter about not updating pg_database for each table
when called by autovacuum, and do it only once the whole autovacuum iteration
is done.
I updated the system catalogs documentation, but I didn't modify the
maintenance section. Also having some regression tests for this would be nice
but it's not really a very straightforward thing to do.
Catalog version bumped due to system catalog changes.
|
