aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
* Add more explicit note that the parameters of MOVE are identical to FETCH.Peter Eisentraut2009-06-22
| | | | per David Wheeler
* Fix things so that array_agg_finalfn does not modify or free its inputTom Lane2009-06-20
| | | | | | | ArrayBuildState, per trouble report from Merlin Moncure. By adopting this fix, we are essentially deciding that aggregate final-functions should not modify their inputs ever. Adjust documentation and comments to match that conclusion.
* Don't convert the man page names to lower case, so that the .so links work.Peter Eisentraut2009-06-19
| | | | | This is pretty much a workaround for incomplete tools, but having the man page names in upper case looks more natural anyway.
* Add manvolnum, so that man pages are generated.Peter Eisentraut2009-06-19
|
* Recursive Joins -> Recursive QueriesPeter Eisentraut2009-06-18
| | | | per Erik Rijkers
* Add some more documentation and cross-links on using dblink with SQL/MED.Peter Eisentraut2009-06-18
|
* Refine the use of terminology around bound and unbound cursors and cursorPeter Eisentraut2009-06-18
| | | | variables. Remove the confusing term "reference cursor".
* Proofreading for Bruce's recent round of documentation proofreading.Tom Lane2009-06-17
| | | | Most of those changes were good, but some not so good ...
* Add another link of a GUC variable to where it is explained.Peter Eisentraut2009-06-17
|
* Improve documentation about GiST opclass support functions.Tom Lane2009-06-12
| | | | Dimitri Fontaine
* Add info about minimum recommended AIX fix levels, per Laurenz Albe.Tom Lane2009-06-12
|
* Update release notes to today.Tom Lane2009-06-11
|
* Remove our inadequate kluge that tried to get AIX's various broken versionsTom Lane2009-06-11
| | | | | of getaddrinfo() to work. Instead, recommend updating the OS to get a working version of getaddrinfo. Per recent discussions.
* Add warning that xpath() doesn't work with non-UTF8 data.Tom Lane2009-06-10
|
* Add a warning about possible strange behavior of volatile functionsTom Lane2009-06-10
| | | | | in cursors. This has always been the case, but given the lack of user complaints about it, I'm not going to bother back-patching this.
* Correct/improve the datetime_precision field in the information schema.Peter Eisentraut2009-06-10
| | | | | | | | | | In particular, always show 0 for the date type instead of null, and show 6 (the default) for time, timestamp, and interval without a declared precision. This is now in fuller conformance with the SQL standard. Also clarify the documentation about this. discovered and analyzed by Konstantin Izmailov and Tom Lane
* Fix contrib/pageinspect to not create an ABI breakage between 8.3 and 8.4.Tom Lane2009-06-08
| | | | | | | | | | The original implementation of the 3-argument form of get_raw_page() risked core dumps if the 8.3 SQL function definition was mistakenly used with the 8.4 module, which is entirely likely after a dump-and-reload upgrade. To protect 8.4 beta testers against upgrade problems, add a check on PG_NARGS. In passing, fix missed additions to the uninstall script, and polish the docs a trifle.
* Be a bit more verbose about the effects of string literal processingTom Lane2009-06-08
| | | | changes in plpgsql. Per bug #4843.
* Revert my patch of 2009-04-04 that removed contrib/intarray's definitions ofTom Lane2009-06-07
| | | | | | | | | | | the <@ and @> operators. These are not in fact equivalent to the built-in anyarray operators of the same names, because they have different behavior for empty arrays, namely they don't think empty arrays are contained in anything. That is mathematically wrong, no doubt, but until we can persuade GIN indexes to implement the mathematical definition we should probably not change this. Another reason for not changing it now is that we can't yet ensure the opclasses will be updated correctly in a dump-and-reload upgrade. Per recent discussions.
* Add support for using SQL/MED compliant FOREIGN DATA WRAPPER, SERVER,Joe Conway2009-06-06
| | | | | and USER MAPPING as method to supply dblink connect parameters. Per mailing list and PGCon discussions.
* Remove sleep() from backup script example; not needed anymore.Bruce Momjian2009-06-05
| | | | Fujii Masao
* Improve the recently-added support for properly pluralized error messagesTom Lane2009-06-04
| | | | | | | | | | by extending the ereport() API to cater for pluralization directly. This is better than the original method of calling ngettext outside the elog.c code because (1) it avoids double translation, which wastes cycles and in the worst case could give a wrong result; and (2) it avoids having to use a different coding method in PL code than in the core backend. The client-side uses of ngettext are not touched since neither of these concerns is very pressing in the client environment. Per my proposal of yesterday.
* Wording improvement for recent sesssion identifier SQL query.Bruce Momjian2009-06-03
|
* Add example of how to generate the session identifier from pg_stat_activity.Bruce Momjian2009-06-03
|
* Remove the old advice to keep from_collapse_limit less than geqo_threshold,Tom Lane2009-06-02
| | | | | | | instead just pointing out that a larger value may trigger use of GEQO. Per Robert Haas. In passing, do a bit of wordsmithing on the Genetic Query Optimizer section.
* Document that forking while having open libpq connections is notBruce Momjian2009-05-28
| | | | advised.
* Improve release note explanation of the change in libpq's handling ofTom Lane2009-05-27
| | | | | default usernames versus Kerberos tickets. Per confusion about what bug #4824 was really about.
* Remove tabs from SGML file.Bruce Momjian2009-05-27
|
* Improve documentation about function volatility: mention the snapshotTom Lane2009-05-27
| | | | | visibility effects in a couple of places where people are likely to look for it. Per discussion of recent question from Karl Nack.
* Allow the second argument of pg_get_expr() to be just zero when deparsingTom Lane2009-05-26
| | | | | | | an expression that's not supposed to contain variables. Per discussion with Gevik Babakhani, this eliminates the need for an ugly kluge (namely, specifying some unrelated relation name). Remove one such kluge from pg_dump.
* Refer to tables by id, not by "the following table", because tables are inPeter Eisentraut2009-05-18
| | | | theory floating elements.
* Some documentation cleanup for the addition of the KOI8U encoding. ChangePeter Eisentraut2009-05-18
| | | | | all (remaining) mentions of KOI8 to the new canonical form KOI8R. Add information about the available conversions for KOI8U.
* Minor copy-editing for description of partial-table vacuuming.Tom Lane2009-05-16
|
* Minor editorialization on storage.sgml's documentation of free spaceTom Lane2009-05-16
| | | | maps.
* Make an editorial pass over the Client Authentication material.Tom Lane2009-05-16
|
* Update release notes to today.Tom Lane2009-05-14
|
* Clean up overly hasty docs patch for pg_standby.Tom Lane2009-05-14
|
* Add a note to release notes about the smart failover mode in pg_standby.Heikki Linnakangas2009-05-14
|
* Add recovery_end_command option to recovery.conf. recovery_end_commandHeikki Linnakangas2009-05-14
| | | | | | | | | | | | | | is run at the end of archive recovery, providing a chance to do external cleanup. Modify pg_standby so that it no longer removes the trigger file, that is to be done using the recovery_end_command now. Provide a "smart" failover mode in pg_standby, where we don't fail over immediately, but only after recovering all unapplied WAL from the archive. That gives you zero data loss assuming all WAL was archived before failover, which is what most users of pg_standby actually want. recovery_end_command by Simon Riggs, pg_standby changes by Fujii Masao and myself.
* Remove a useless backslash from a pattern-match example. Michael ToewsTom Lane2009-05-13
|
* Update release notes for changes through 2009-05-11. Also some minorTom Lane2009-05-12
| | | | copy-editing and reordering of items.
* Move crypt auth comment to proper section.Magnus Hagander2009-05-11
| | | | Add some details about the name=value format of auth options.
* Edit the SSL and Kerberos parts of the release notes a bit, and addMagnus Hagander2009-05-11
| | | | a note about the certificates chains patch just applied.
* Change pgbench to use the table names pgbench_accounts, pgbench_branches,Tom Lane2009-05-07
| | | | | | | | | | | pgbench_history, and pgbench_tellers, rather than just accounts, branches, history, and tellers. This is to prevent accidental conflicts with real application tables, as has been reported to happen at least once. Also remove the automatic "SET search_path = public" that it did at startup, as this seems to restrict testing flexibility without actually buying much. Per proposal by Joshua Drake and ensuing discussion. Joshua Drake and Tom Lane
* Modify CREATE DATABASE to enforce that the source database's encoding settingTom Lane2009-05-06
| | | | | | | | | | | | must be used for the new database, except when copying from template0. This is the same rule that we now enforce for locale settings, and it has the same motivation: databases other than template0 might contain data that would be invalid according to a different setting. This represents another step in a continuing process of locking down ways in which encoding violations could occur inside the backend. Per discussion of a few days ago. In passing, fix pre-existing breakage of mbregress.sh, and fix up a couple of ereport() calls in dbcommands.c that failed to specify sqlstate codes.
* Disable the use of Unicode escapes in string constants (U&'') whenPeter Eisentraut2009-05-05
| | | | standard_conforming_strings is not on, for security reasons.
* Fix mis-description of XML Schema functions, per discussion.Tom Lane2009-05-03
|
* Fix unintelligible description created by removing only part ofTom Lane2009-05-03
| | | | a parenthetical remark.
* Split the release notes into a separate file for each (active) major branch,Tom Lane2009-05-02
| | | | | | | | | | | | as per my recent proposal. release.sgml itself is now just a stub that should change rarely; ideally, only once per major release to add a new include line. Most editing work will occur in the release-N.N.sgml files. To update a back branch for a minor release, just copy the appropriate release-N.N.sgml file(s) into the back branch. This commit doesn't change the end-product documentation at all, only the source layout. However, it makes it easy to start omitting ancient information from newer branches' documentation, should we ever decide to do that.
* Fix plpgsql's EXIT so that an EXIT without a label only matches a loop,Tom Lane2009-05-02
| | | | | | | | | | never a BEGIN block. This is required for Oracle compatibility and is also plainly stated to be the behavior by our original documentation (up until 8.1, in which the docs were adjusted to match the code's behavior; but actually the old docs said the correct thing and the code was wrong). Not back-patched because this introduces an incompatibility that could break working applications. Requires release note.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 15:37:11 +0000