summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
2013-05-06Desultory copy-editing of the 9.3 release notes.Tom Lane
I had time for a quick review of the notes, so here are some fixes.
2013-05-06Move materialized views' is-populated status into their pg_class entries.Tom Lane
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.
2013-05-06Disallow unlogged materialized views.Tom Lane
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.
2013-05-069.3 release notes: use "restoration"Bruce Momjian
Andrew Dunstan
2013-05-069.3 release notes: Add cache of local locksBruce Momjian
Mention this also helps in the restoring of pg_dumps. Jeff Janes
2013-05-069.3 release notes: update from Amit KapilaBruce Momjian
No need to mention wal_receiver_status_interval.
2013-05-06Revert idea of zer-padding padding session id in log_line_prefixBruce Momjian
Removal of doc adjustment and release note mention as well.
2013-05-04docs: Improve log_line_prefix session_id queryBruce Momjian
2013-05-04docs: log_line_prefix session id fixBruce Momjian
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
2013-05-049.3 docs: wording fixesBruce Momjian
From Erik Rijkers
2013-05-04docs: fix log_line_prefix session id docsBruce Momjian
Backpatch to 9.2. Report from Ian Lawrence Barwick
2013-05-049.3 release notes: adjustmentsBruce Momjian
Fixes from Peter Geoghegan, Ian Lawrence Barwick, Marti Raudsepp
2013-05-039.3 release notes: move compatibility items into their own sectionBruce Momjian
2013-05-039.3 release notes: Add markup for pg_backup_start_time()Bruce Momjian
2013-05-039.3 release notes: Add links to SGML sectionsBruce Momjian
2013-05-039.3 release notes: add markup for textBruce Momjian
Still need to add links for new features.
2013-05-03Improve SPI documentation about null-flags arrays.Tom Lane
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.
2013-05-039.3 release notes: update for current commitsBruce Momjian
Also, remove broken link in release.sgml.
2013-05-029.3 release notes: suggested improvements from Jeff Janes and Josh BerkusBruce Momjian
2013-04-29Revert "pg_ctl: Add idempotent option"Peter Eisentraut
This reverts commit 87306184580c9c49717b00d48a2f9e717f21e0a8. The behavior in certain cases is still being debated, and it's too late to solve this before beta.
2013-04-29Attempt to fix error recovery in COPY BOTH mode.Robert Haas
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.
2013-04-24PL/pgSQL doc: Add example for RETURN QUERYPeter Eisentraut
Erwin Brandstetter and Pavel Stěhule
2013-04-239.3 release notes: adjustments per AlvaroBruce Momjian
2013-04-239.3 release note updates from Dean Rasheed, Jov, Heikki Linnakangas,Bruce Momjian
Erikjan Rijkers
2013-04-229.3 release notes: add diacriticsBruce Momjian
Alvaro Herrera
2013-04-229.3 release notes: adjustments per Alvaro and RobertBruce Momjian
2013-04-22Mention in docs that you can create SP-GiST indexes on range types.Heikki Linnakangas
This is new in 9.3devel.
2013-04-229.3 release notes: apply fixes suggested by AlvaroBruce Momjian
2013-04-229.3 release notes: update streaming replication speedupsBruce Momjian
Andres Freund
2013-04-21doc: Improve example formattingPeter Eisentraut
Erwin Brandstetter
2013-04-21doc: Fix syntax in examplePeter Eisentraut
LANGUAGE 'plpgsql' no longer works. The single quotes need to be removed. Erwin Brandstetter
2013-04-21In 9.3 release notes, split up itemsBruce Momjian
Split log shipping speed improvement and fail-over speed improvement items. Per request from Simon
2013-04-219.3 release note adjustments per request from Andres FreundBruce Momjian
2013-04-21Remove 9.3 item about fixing DROP INDEX CONCURRENTLYBruce Momjian
Already fixed in back branch.
2013-04-219.3 release note fixesBruce Momjian
Move commit_delay, fix Zoltan's name, and adjust range type histogram text.
2013-04-21Adjust 9.3 release notes per request from SimonBruce Momjian
2013-04-21Reorder 9.3 release note itemsBruce Momjian
Typo fix from David Fetter.
2013-04-20More 9.3 release note reorderingsBruce Momjian
2013-04-20Fix Gilles Darold's name in 9.3 release notes.Bruce Momjian
2013-04-20Reorder some 9.3 release item entriesBruce Momjian
More to go.
2013-04-20Push 9.3 release SGML fileBruce Momjian
Forgotten in previous commit.
2013-04-20Publish draft 9.3 release notesBruce Momjian
No links added yet.
2013-04-20doc: Mention SATA alongside IDE for LinuxPeter Eisentraut
suggested by Jov
2013-04-18Standardize spelling of "nonblocking"Peter Eisentraut
Only adjusted the user-exposed messages and documentation, not all source code comments.
2013-04-17sepgsql: Minor improvement to test script, doc fix.Robert Haas
KaiGai Kohei
2013-04-16doc: Update PQgetssl() documentationPeter Eisentraut
The return type of PQgetssl() was changed from SSL* to void* a long time ago, but the documentation was not updated.
2013-04-13pg_ctl: Add idempotent optionPeter Eisentraut
This changes the behavior of the start and stop actions to exit successfully if the server was already started or stopped. This changes the default behavior of the start action: Before, if the server was already running, it would print a message and succeed. Now, that situation will result in an error. When running in idempotent mode, no message is printed and pg_ctl exits successfully. It was considered to just make the idempotent behavior the default and only option, but pg_upgrade needs the old behavior.
2013-04-12sepgsql: Enforce db_procedure:{execute} permission.Robert Haas
To do this, we add an additional object access hook type, OAT_FUNCTION_EXECUTE. KaiGai Kohei
2013-04-10doc: Update DTrace informationPeter Eisentraut
The old web site link no longer worked, and some information was outdated.
2013-04-10Update the description for the graphical installersMagnus Hagander
Remove references to "one click", as we're not supposed to call them that anymore.