summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
2008-04-15Add TODO item:Bruce Momjian
< * 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
2008-04-15Move LISTEN/NOTIFY items to separate TODO section.Bruce Momjian
2008-04-15Add to TODO:Bruce Momjian
> * Allow XML to accept more liberal DOCTYPE specifications > > http://archives.postgresql.org/pgsql-general/2008-02/msg00347.php
2008-04-15Done:Bruce Momjian
> * -Allow administrators to safely terminate individual sessions either
2008-04-15Add pg_terminate_backend() to allow terminating only a single session.Bruce Momjian
2008-04-14Push index operator lossiness determination down to GIST/GIN opclassTom Lane
"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.
2008-04-14Add URL for:Bruce Momjian
* Consider automatic caching of statements at various levels: > http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php
2008-04-13Phase 2 of project to make index operator lossiness be determined at runtimeTom Lane
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.
2008-04-13Turn the -i/--ignore-version options of pg_dump and pg_dumpall into no-ops:Tom Lane
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.
2008-04-11Update wording:Bruce Momjian
< * Allow functions to control the transaction state > * Allow calling of a procedure outside a SELECT that can control the > transaction state
2008-04-11Changed TODO wording:Bruce Momjian
< * Support procedures, which return no value > * Allow functions to control the transaction state
2008-04-11Add TODO:Bruce Momjian
> * Support procedures, which return no value > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01375.php
2008-04-11Update URLs for dead space map.Bruce Momjian
2008-04-10Replace "amgetmulti" AM functions with "amgetbitmap", in which the wholeTom Lane
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.
2008-04-10Add TODO URLs moved from open items queue:Bruce Momjian
> 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
2008-04-10Remove mention of DBD::PgSPI, which is unmaintained and generally unnecessary.Alvaro Herrera
2008-04-10Mention pg_backend_pid() in the system information section in additionAlvaro Herrera
to the monitoring section. Jim Nasby
2008-04-09Document that continuous archiving backup can be used for cases whereBruce Momjian
you can't get a simultaneous snapshot.
2008-04-09Update text FAQ.Bruce Momjian
2008-04-09Revert sentence removal from nickname in FAQ.Bruce Momjian
2008-04-09Remove mention of the Berkeley origins of the alias "Postgres" ---Bruce Momjian
seems unnecessary to mention in the FAQ, per discussion on IRC.
2008-04-07Add to TODO:Bruce Momjian
> > o Add ability to obfuscate function bodies > > http://archives.postgresql.org/pgsql-patches/2008-01/msg00125.php
2008-04-07Add documentation clarification for IS [NOT] NULL and row-valuedBruce Momjian
expressions.
2008-04-06Make plpgsql support FOR over a query specified by a cursor declaration,Tom Lane
for improved compatibility with Oracle. Pavel Stehule, with some fixes by me.
2008-04-05Have pg_stop_backup() wait for all archive files to be sent, rather thanBruce Momjian
returing right away. This guarantees that when pg_stop_backup() returns, you have a valid backup. Simon Riggs
2008-04-04Re-implement division for numeric values using the traditional "schoolbook"Tom Lane
algorithm. This is a good deal slower than our old roundoff-error-prone code for long inputs, so we keep the old code for use in the transcendental functions, where everything is approximate anyway. Also create a user-accessible function div(numeric, numeric) to provide access to the exact result of trunc(x/y) --- since the regular numeric / operator will round off its result, simply computing that expression in SQL doesn't reliably give the desired answer. This fixes bug #3387 and various related corner cases, and improves the usefulness of PG for high-precision integer arithmetic.
2008-04-04Implement current_query(), that shows the currently executing query.Bruce Momjian
At the same time remove dblink/dblink_current_query() as it is no longer necessary *BACKWARD COMPATIBILITY ISSUE* for dblink Tomas Doran
2008-04-03Add a variant of the Levenshtein string-distance function that lets the userTom Lane
specify the cost values to use, instead of always using 1's. Volkan Yazici In passing, remove fuzzystrmatch.h, which contained a bunch of stuff that had no business being in a .h file; fold it into its only user, fuzzystrmatch.c.
2008-04-03Add Wiki URLs for:Bruce Momjian
< * Allow encoding on a per-column basis optionally using the ICU library > http://wiki.postgresql.org/wiki/Todo:Collate > http://wiki.postgresql.org/wiki/Todo:ICU
2008-04-03Add to TODO:Bruce Momjian
> * Improve how ANALYZE computes in-doubt tuples > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00771.php >
2008-04-03Remove -C from rsync call, because it omits directories named "core".Peter Eisentraut
2008-04-03Add URLs for:Bruce Momjian
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-patches/2008-01/msg00105.php > http://archives.postgresql.org/pgsql-patches/2008-03/msg00327.php
2008-04-02Remove due to survey/discussion:Bruce Momjian
< < * Prefix command-line utilities like createuser with 'pg_' < < http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php <
2008-04-01Support EXECUTE USING in plpgsql.Tom Lane
Pavel Stehule, with some improvements by myself.
2008-04-01Add SPI-level support for executing SQL commands with one-time-use plans,Tom Lane
that is commands that have out-of-line parameters but the plan is prepared assuming that the parameter values are constants. This is needed for the plpgsql EXECUTE USING patch, but will probably have use elsewhere. This commit includes the SPI functions and documentation, but no callers nor regression tests. The upcoming EXECUTE USING patch will provide regression-test coverage. I thought committing this separately made sense since it's logically a distinct feature.
2008-03-31Use error message wordings for permissions checks on .pgpass and SSL privateTom Lane
key files that are similar to the one for the postmaster's data directory permissions check. (I chose to standardize on that one since it's the most heavily used and presumably best-wordsmithed by now.) Also eliminate explicit tests on file ownership in these places, since the ensuing read attempt must fail anyway if it's wrong, and there seems no value in issuing the same error message for distinct problems. (But I left in the explicit ownership test in postmaster.c, since it had its own error message anyway.) Also be more specific in the documentation's descriptions of these checks. Per a gripe from Kevin Hunter.
2008-03-30Show database access privileges in psql's \l command. For \l+, also showTom Lane
database size, when available to the current user. Andrew Gilligan
2008-03-30Enable 64-bit integer datetimes by default, per previous discussion.Neil Conway
This requires a working 64-bit integer type. If such a type cannot be found, "--disable-integer-datetimes" can be used to switch back to the previous floating point-based datetime implementation.
2008-03-28Done:Bruce Momjian
> * -Add ability to trigger on TRUNCATE
2008-03-28Clarify documentation on PITR and warm standby on the fact that the standbyHeikki Linnakangas
restore_command should report failure on non-existent .backup and .history files. Tidy up some related text along the way. Patch by Markus Bertheau, with some editing by Simon Riggs and myself.
2008-03-28Add to TODO:Bruce Momjian
> > o Add CASE capability to language (already in SQL) > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00696.php > >
2008-03-28Add:Bruce Momjian
> * Allow one transaction to see tuples using the snapshot of another > transaction > > This would assist multiple backends in working together. > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00400.php
2008-03-28Support statement-level ON TRUNCATE triggers. Simon RiggsTom Lane
2008-03-27Add to TODO:Bruce Momjian
> > * Consider being smarter about memory and external files used during > sorts > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg01101.php > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00045.php
2008-03-27Add URL for:Bruce Momjian
* Consider allowing control of upper/lower case folding of unquoted identifiers > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00849.php
2008-03-27Remove ipcclean utility command --- didn't work on all Unixes and onBruce Momjian
Windows. Users should use their operating system tools instead.
2008-03-26Fix bad spelling and worse grammar in recent doc commits. PropagateTom Lane
pg_dump --ignore-version comments into pg_dumpall and pg_restore pages.
2008-03-26Improve documentation for odd array slice behavior.Bruce Momjian
2008-03-26Strengthen warnings about using pg_dump's -i option.Bruce Momjian
2008-03-26Update TODO:Bruce Momjian
< o Consider invalidating the cache or keeping seperate cached < copies when search_path changes > o Consider keeping seperate cached copies when search_path changes
generated by cgit v1.2.3 (git 2.46.0) at 2025-09-30 00:39:15 +0000