aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Minor docs wordsmithing.Tom Lane2013-06-07
| | | | | | | Swap the order of a couple of phrases to clarify what the adjective "subsequent" applies to. Joshua Tolley
* doc: Clarify description of VALUES commandPeter Eisentraut2013-06-06
| | | | Greg Smith
* pg_upgrade: document that --link should be used with --checkBruce Momjian2013-06-06
| | | | Backpatch to 9.2.
* Another man page whitespace fixPeter Eisentraut2013-06-01
|
* Fix whitespace issues in the man pagesPeter Eisentraut2013-06-01
| | | | See 00b0c73f1f2b98a7d09de63aaa14d6498ac521ae for an explanation.
* doc: Remove paragraph about typesetting conventionsPeter Eisentraut2013-05-31
| | | | | They no longer match reality with the web site style sheets, and it is difficult to keep the up to date in a CSS world.
* doc: Fix claim that query is passed as ASCII textPeter Eisentraut2013-05-30
| | | | Ian Lawrence Barwick
* Remove whitespace from end of linesPeter Eisentraut2013-05-30
|
* Document auto_explain.log_timing.Robert Haas2013-05-29
| | | | Tomas Vondra
* pg_upgrade docs: mention need to set parameters for vacuumdb.Bruce Momjian2013-05-28
|
* Documentation fix for ALTER TYPE .. RENAMEStephen Frost2013-05-27
| | | | | | | | | | | | The documentation for ALTER TYPE .. RENAME claimed to support a RESTRICT/CASCADE option at the 'type' level, which wasn't implemented and doesn't make a whole lot of sense to begin with. What is supported, and previously undocumented, is ALTER TYPE .. RENAME ATTRIBUTE .. RESTRICT/CASCADE. I've updated the documentation and back-patched this to 9.1 where it was first introduced.
* 9.3 release notes: improve cached plan mentionBruce Momjian2013-05-21
| | | | Per suggestion from Tom Lane.
* 9.3 release notes: fix SGML markup for DROP TABLE IF EXISTSBruce Momjian2013-05-21
|
* 9.3 release docs: fix DROP TABLE IF EXISTSBruce Momjian2013-05-20
| | | | Patch from Joe Abbate.
* Documentation spell checking and markup improvementsPeter Eisentraut2013-05-20
|
* Clarify documentation of EXPLAIN (TIMING OFF) option.Tom Lane2013-05-19
| | | | | | | Clarify that this option doesn't suppress measurement of the statement's total runtime. Greg Smith
* release docs: mention PL/pgSQL as supporting event triggers in PG 9.3Bruce Momjian2013-05-18
|
* Fix some uses of "the quick brown fox".Tom Lane2013-05-16
| | | | | If we're going to quote a well-known pangram, we should quote it accurately. Per gripe from Thom Brown.
* doc: Add \dm command to psql man pagePeter Eisentraut2013-05-14
|
* doc: Fix some whitespace issues in the man pagesPeter Eisentraut2013-05-13
|
* doc: Fix order of options on pgbench man pagePeter Eisentraut2013-05-13
|
* Update CREATE FUNCTION documentation about argument names.Tom Lane2013-05-11
| | | | | | The 9.2 patch that added argument name support in SQL-language functions missed updating a parenthetical comment about that in the CREATE FUNCTION reference page. Noted by Erwin Brandstetter.
* Update key words table for 9.3Peter Eisentraut2013-05-09
|
* pg_upgrade docs: give tips on automationBruce Momjian2013-05-09
| | | | | | Document that post-upgrade steps are likely to be the same for all clusters with the same DDL/schemas; this should help automated upgrades.
* Fix walsender failure at promotion.Heikki Linnakangas2013-05-08
| | | | | | | | | | | | | | | | | | | | | | | | If a standby server has a cascading standby server connected to it, it's possible that WAL has already been sent up to the next WAL page boundary, splitting a WAL record in the middle, when the first standby server is promoted. Don't throw an assertion failure or error in walsender if that happens. Also, fix a variant of the same bug in pg_receivexlog: if it had already received WAL on previous timeline up to a segment boundary, when the upstream standby server is promoted so that the timeline switch record falls on the previous segment, pg_receivexlog would miss the segment containing the timeline switch. To fix that, have walsender send the position of the timeline switch at end-of-streaming, in addition to the next timeline's ID. It was previously assumed that the switch happened exactly where the streaming stopped. Note: this is an incompatible change in the streaming protocol. You might get an error if you try to stream over timeline switches, if the client is running 9.3beta1 and the server is more recent. It should be fine after a reconnect, however. Reported by Fujii Masao.
* Use the term "radix tree" instead of "suffix tree" for SP-GiST text opclass.Heikki Linnakangas2013-05-08
| | | | | | | What we have implemented is a radix tree (or a radix trie or a patricia trie), but the docs and code comments incorrectly called it a "suffix tree". Alexander Korotkov
* doc: Add IDs to link targets used by phpPgAdminPeter Eisentraut2013-05-07
| | | | Karl O. Pinc
* Stress that backup_label file is critical in the docs.Heikki Linnakangas2013-05-07
| | | | | | | It is surprisingly common mistake to leave out backup_label file from a base backup. Say more explicitly that it must be included. Jeff Janes, with minor rewording by me.
* Desultory copy-editing of the 9.3 release notes.Tom Lane2013-05-06
| | | | I had time for a quick review of the notes, so here are some fixes.
* Move materialized views' is-populated status into their pg_class entries.Tom Lane2013-05-06
| | | | | | | | | | | | Previously this state was represented by whether the view's disk file had zero or nonzero size, which is problematic for numerous reasons, since it's breaking a fundamental assumption about heap storage. This was done to allow unlogged matviews to revert to unpopulated status after a crash despite our lack of any ability to update catalog entries post-crash. However, this poses enough risk of future problems that it seems better to not support unlogged matviews until we can find another way. Accordingly, revert that choice as well as a number of existing kluges forced by it in favor of creating a pg_class.relispopulated flag column.
* Disallow unlogged materialized views.Tom Lane2013-05-06
| | | | | | | | | | | | | | | | | The initial implementation of this feature was really unsupportable, because it's relying on the physical size of an on-disk file to carry the relation's populated/unpopulated state, which is at least a modularity violation and could have serious long-term consequences. We could say that an unlogged matview goes to empty on crash, but not everybody likes that definition, so let's just remove the feature for 9.3. We can add it back when we have a less klugy implementation. I left the grammar and tab-completion support for CREATE UNLOGGED MATERIALIZED VIEW in place, since it's harmless and allows delivering a more specific error message about the unsupported feature. I'm committing this separately to ease identification of what should be reverted when/if we are able to re-enable the feature.
* 9.3 release notes: use "restoration"Bruce Momjian2013-05-06
| | | | Andrew Dunstan
* 9.3 release notes: Add cache of local locksBruce Momjian2013-05-06
| | | | | | Mention this also helps in the restoring of pg_dumps. Jeff Janes
* 9.3 release notes: update from Amit KapilaBruce Momjian2013-05-06
| | | | No need to mention wal_receiver_status_interval.
* Revert idea of zer-padding padding session id in log_line_prefixBruce Momjian2013-05-06
| | | | Removal of doc adjustment and release note mention as well.
* docs: Improve log_line_prefix session_id queryBruce Momjian2013-05-04
|
* docs: log_line_prefix session id fixBruce Momjian2013-05-04
| | | | | | | | | Restore 4-byte designation for docs. Fix 9.3 doc query to properly pad to four digits. Backpatch to all active branches Per suggestions from Ian Lawrence Barwick
* 9.3 docs: wording fixesBruce Momjian2013-05-04
| | | | From Erik Rijkers
* docs: fix log_line_prefix session id docsBruce Momjian2013-05-04
| | | | | | Backpatch to 9.2. Report from Ian Lawrence Barwick
* 9.3 release notes: adjustmentsBruce Momjian2013-05-04
| | | | Fixes from Peter Geoghegan, Ian Lawrence Barwick, Marti Raudsepp
* 9.3 release notes: move compatibility items into their own sectionBruce Momjian2013-05-03
|
* 9.3 release notes: Add markup for pg_backup_start_time()Bruce Momjian2013-05-03
|
* 9.3 release notes: Add links to SGML sectionsBruce Momjian2013-05-03
|
* 9.3 release notes: add markup for textBruce Momjian2013-05-03
| | | | Still need to add links for new features.
* Improve SPI documentation about null-flags arrays.Tom Lane2013-05-03
| | | | | | Clarify the description of nulls[] arguments, and use the same wording for all SPI functions with this type of argument. Per gripe from Yuriy Rusinov.
* 9.3 release notes: update for current commitsBruce Momjian2013-05-03
| | | | Also, remove broken link in release.sgml.
* 9.3 release notes: suggested improvements from Jeff Janes and Josh BerkusBruce Momjian2013-05-02
|
* Revert "pg_ctl: Add idempotent option"Peter Eisentraut2013-04-29
| | | | | | This reverts commit 87306184580c9c49717b00d48a2f9e717f21e0a8. The behavior in certain cases is still being debated, and it's too late to solve this before beta.
* Attempt to fix error recovery in COPY BOTH mode.Robert Haas2013-04-29
| | | | | | | | | | | | | | | | | | | | | | Previously, libpq and the backend had opposite ideas about whether it was necessary for the client to send a CopyDone message after receiving an ErrorResponse, making it impossible to cleanly exit COPY BOTH mode. Fix libpq so that works correctly, adopting the backend's notion that an ErrorResponse kills the copy in both directions. Adjust receivelog.c to avoid a degradation in the quality of the resulting error messages. libpqwalreceiver.c is already doing the right thing, so no adjustment needed there. Add an explicit statement to the documentation explaining how this part of the protocol is supposed to work, in the hopes of avoiding future confusion in this area. Since the consequences of all this confusion are very limited, especially in the back-branches where no client ever attempts to exit COPY BOTH mode without closing the connection entirely, no back-patch.
* PL/pgSQL doc: Add example for RETURN QUERYPeter Eisentraut2013-04-24
| | | | Erwin Brandstetter and Pavel Stěhule
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-20 22:43:37 +0000