| Age | Commit message (Collapse) | Author |
|
< * Allow adding enumerated values to an existing enumerated data
> * Allow adding/removing enumerated values to an existing enumerated data
|
|
|
|
> * Allow prepared transactions with temporary tables created and dropped
> in the same transaction, and when an ON COMMIT DELETE ROWS temporary
> table is accessed
>
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00047.php
|
|
>
> o Impove COPY performance
>
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg00954.php
|
|
* Allow index scans to return matching index keys, not just the matching
heap locations
>
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg01657.php
>
|
|
> * Allow index scans to return matching index keys, not just the matching
> heap locations
|
|
<
> * Allow adding enumerated values to an existing enumerated data
> type
|
|
< * Allow index scans to return matching index keys
<
< http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php
|
|
* Consider smaller indexes that record a range of values per heap page,
rather than having one index entry for every heap row
|
|
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg01589.php
|
|
<
> o Add prompt escape to display the client and server versions
|
|
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg01475.php
|
|
have pg_ctl warn about this.
Cancel running online backups (by renaming the backup_label file,
thus rendering the backup useless) when shutting down in fast mode.
Laurenz Albe
|
|
it now lives (per discussion). Leave the other FAQs alone for now.
|
|
|
|
version ones, to make it clear to users just browsing the notes
that there are a lot more changes available from whatever version
they are at than what's in the minor version release notes.
|
|
where Datum is 8 bytes wide. Since this will break old-style C functions
(those still using version 0 calling convention) that have arguments or
results of these types, provide a configure option to disable it and retain
the old pass-by-reference behavior. Likewise, provide a configure option
to disable the recently-committed float4 pass-by-value change.
Zoltan Boszormenyi, plus configurability stuff by me.
|
|
|
|
archives. We have been using URLs for a while for new items.
|
|
of each plan node, instead of its former behavior of dumping the internal
representation of the plan tree. The latter display is still available for
those who really want it (see debug_print_plan), but uses for it are certainly
few and and far between. Per discussion.
This patch also removes the explain_pretty_print GUC, which is obsoleted
by the change.
|
|
> * -Allow administrators to safely terminate individual sessions
|
|
needed.
|
|
|
|
|
|
> * Implement the non-threaded Avahi service discovery protocol
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg00939.php
> http://archives.postgresql.org/pgsql-patches/2008-02/msg00097.php
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg01211.php
> http://archives.postgresql.org/pgsql-patches/2008-04/msg00001.php
|
|
|
|
|
|
< * Allow NOTIFY in rules involving conditionals
>
> o Allow NOTIFY in rules involving conditionals
> o Improve LISTEN concurrency
>
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg01106.php
|
|
|
|
> * Allow XML to accept more liberal DOCTYPE specifications
>
> http://archives.postgresql.org/pgsql-general/2008-02/msg00347.php
|
|
> * -Allow administrators to safely terminate individual sessions either
|
|
|
|
"consistent" functions, and remove pg_amop.opreqcheck, as per recent
discussion. The main immediate benefit of this is that we no longer need
8.3's ugly hack of requiring @@@ rather than @@ to test weight-using tsquery
searches on GIN indexes. In future it should be possible to optimize some
other queries better than is done now, by detecting at runtime whether the
index match is exact or not.
Tom Lane, after an idea of Heikki's, and with some help from Teodor.
|
|
* Consider automatic caching of statements at various levels:
> http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php
|
|
instead of plan time. Extend the amgettuple API so that the index AM returns
a boolean indicating whether the indexquals need to be rechecked, and make
that rechecking happen in nodeIndexscan.c (currently the only place where
it's expected to be needed; other callers of index_getnext are just erroring
out for now). For the moment, GIN and GIST have stub logic that just always
sets the recheck flag to TRUE --- I'm hoping to get Teodor to handle pushing
that control down to the opclass consistent() functions. The planner no
longer pays any attention to amopreqcheck, and that catalog column will go
away in due course.
|
|
the server version check is now always enforced. Relax the version check to
allow a server that is of pg_dump's own major version but a later minor
version; this is the only case that -i was at all safe to use in.
pg_restore already enforced only a very weak version check, so this is
really just a documentation change for it.
Per discussion.
|
|
< * Allow functions to control the transaction state
> * Allow calling of a procedure outside a SELECT that can control the
> transaction state
|
|
< * Support procedures, which return no value
> * Allow functions to control the transaction state
|
|
> * Support procedures, which return no value
>
> http://archives.postgresql.org/pgsql-hackers/2007-10/msg01375.php
|
|
|
|
indexscan always occurs in one call, and the results are returned in a
TIDBitmap instead of a limited-size array of TIDs. This should improve
speed a little by reducing AM entry/exit overhead, and it is necessary
infrastructure if we are ever to support bitmap indexes.
In an only slightly related change, add support for TIDBitmaps to preserve
(somewhat lossily) the knowledge that particular TIDs reported by an index
need to have their quals rechecked when the heap is visited. This facility
is not really used yet; we'll need to extend the forced-recheck feature to
plain indexscans before it's useful, and that hasn't been coded yet.
The intent is to use it to clean up 8.3's horrid @@@ kluge for text search
with weighted queries. There might be other uses in future, but that one
alone is sufficient reason.
Heikki Linnakangas, with some adjustments by me.
|
|
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php
> http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php
> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00014.php
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00487.php
> * Allow index scans to return matching index keys
>
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php
>
> http://archives.postgresql.org/pgsql-patches/2007-10/msg00166.php
> http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php
|
|
|
|
to the monitoring section.
Jim Nasby
|
|
you can't get a simultaneous snapshot.
|
|
|
|
|
|
seems unnecessary to mention in the FAQ, per discussion on IRC.
|
|
>
> o Add ability to obfuscate function bodies
>
> http://archives.postgresql.org/pgsql-patches/2008-01/msg00125.php
|
|
expressions.
|