summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
2013-06-24Reverting previous commit, pending investigationSimon Riggs
of sporadic seg faults from various build farm members.
2013-06-24ALTER TABLE ... ALTER CONSTRAINT for FKsSimon Riggs
Allow constraint attributes to be altered, so the default setting of NOT DEFERRABLE can be altered to DEFERRABLE and back. Review by Abhijit Menon-Sen
2013-06-21doc: Fix date in EPUB manifestPeter Eisentraut
If there is no <date> element, the publication date for the EPUB manifest is taken from the copyright year. But something like "1996-2013" is not a legal date specification. So the EPUB output currently fails epubcheck. Put in a separate <date> element with the current year. Put it in legal.sgml, because copyright.pl already instructs to update that manually, so it hopefully won't be missed.
2013-06-20Clarify terminology standalone backend vs. single-user modePeter Eisentraut
Most of the documentation uses "single-user mode", so use that in the code as well. Adjust the documentation to match the new error message wording. Also add a documentation index entry for "single-user mode". Based-on-patch-by: Jeff Janes <jeff.janes@gmail.com>
2013-06-19Further update CREATE FUNCTION documentation about argument namesPeter Eisentraut
More languages than SQL and PL/pgSQL actually support parameter names.
2013-06-20Support TB (terabyte) memory unit in GUC variables.Fujii Masao
Patch by Simon Riggs, reviewed by Jeff Janes and me.
2013-06-18Fix docs on lock level for ALTER TABLE VALIDATESimon Riggs
ALTER TABLE .. VALIDATE CONSTRAINT previously gave incorrect details about lock levels and therefore incomplete reasons to use the option. Initial bug report and fix from Marko Tiikkaja Reworded by me to include comments by Kevin Grittner
2013-06-16Fix description of archive format which pg_restore -j supports.Fujii Masao
2013-06-14Add :client_id automatic variable for custom pgbench scripts.Heikki Linnakangas
This makes it easier to write custom scripts that have different logic for each client. Gurjeet Singh, with some changes by me.
2013-06-12Improve updatability checking for views and foreign tables.Tom Lane
Extend the FDW API (which we already changed for 9.3) so that an FDW can report whether specific foreign tables are insertable/updatable/deletable. The default assumption continues to be that they're updatable if the relevant executor callback function is supplied by the FDW, but finer granularity is now possible. As a test case, add an "updatable" option to contrib/postgres_fdw. This patch also fixes the information_schema views, which previously did not think that foreign tables were ever updatable, and fixes view_is_auto_updatable() so that a view on a foreign table can be auto-updatable. initdb forced due to changes in information_schema views and the functions they rely on. This is a bit unfortunate to do post-beta1, but if we don't change this now then we'll have another API break for FDWs when we do change it. Dean Rasheed, somewhat editorialized on by Tom Lane
2013-06-12Fix unescaping of JSON Unicode escapes, especially for non-UTF8.Andrew Dunstan
Per discussion on -hackers. We treat Unicode escapes when unescaping them similarly to the way we treat them in PostgreSQL string literals. Escapes in the ASCII range are always accepted, no matter what the database encoding. Escapes for higher code points are only processed in UTF8 databases, and attempts to process them in other databases will result in an error. \u0000 is never unescaped, since it would result in an impermissible null byte.
2013-06-12Improve description of loread/lowrite.Robert Haas
Patch by me, reviewed by Tatsuo Ishii.
2013-06-11Add description that loread()/lowrite() are corresponding toTatsuo Ishii
lo_read()/lo_write() in libpq to avoid confusion.
2013-06-09Remove ALTER DEFAULT PRIVILEGES' requirement of schema CREATE permissions.Tom Lane
Per discussion, this restriction isn't needed for any real security reason, and it seems to confuse people more often than it helps them. It could also result in some database states being unrestorable. So just drop it. Back-patch to 9.0, where ALTER DEFAULT PRIVILEGES was introduced.
2013-06-08Handle Unicode surrogate pairs correctly when processing JSON.Andrew Dunstan
In 9.2, Unicode escape sequences are not analysed at all other than to make sure that they are in the form \uXXXX. But in 9.3 many of the new operators and functions try to turn JSON text values into text in the server encoding, and this includes de-escaping Unicode escape sequences. This processing had not taken into account the possibility that this might contain a surrogate pair to designate a character outside the BMP. That is now handled correctly. This also enforces correct use of surrogate pairs, something that is not done by the type's input routines. This fact is noted in the docs.
2013-06-07doc: Fix <synopsis> in <term> markupPeter Eisentraut
Although the DTD technically allows this, the resulting HTML is invalid because it puts block elements inside inline elements. DocBook 5.0 also doesn't allow it anymore, so it's fair to assume that this was never really intended to work. Replace <synopsis> with <literal>, which is the markup used elsewhere in the documentation in similar cases.
2013-06-07Correct the documentation of pg_rewrite.ev_attr.Kevin Grittner
It claimed the value was always zero; it is really always -1. Per report from Hari Babu
2013-06-07Minor docs wordsmithing.Tom Lane
Swap the order of a couple of phrases to clarify what the adjective "subsequent" applies to. Joshua Tolley
2013-06-06doc: Clarify description of VALUES commandPeter Eisentraut
Greg Smith
2013-06-06pg_upgrade: document that --link should be used with --checkBruce Momjian
Backpatch to 9.2.
2013-06-01Another man page whitespace fixPeter Eisentraut
2013-06-01Fix whitespace issues in the man pagesPeter Eisentraut
See 00b0c73f1f2b98a7d09de63aaa14d6498ac521ae for an explanation.
2013-05-31doc: Remove paragraph about typesetting conventionsPeter Eisentraut
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.
2013-05-30doc: Fix claim that query is passed as ASCII textPeter Eisentraut
Ian Lawrence Barwick
2013-05-30Remove whitespace from end of linesPeter Eisentraut
2013-05-29Document auto_explain.log_timing.Robert Haas
Tomas Vondra
2013-05-28pg_upgrade docs: mention need to set parameters for vacuumdb.Bruce Momjian
2013-05-27Documentation fix for ALTER TYPE .. RENAMEStephen Frost
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.
2013-05-219.3 release notes: improve cached plan mentionBruce Momjian
Per suggestion from Tom Lane.
2013-05-219.3 release notes: fix SGML markup for DROP TABLE IF EXISTSBruce Momjian
2013-05-209.3 release docs: fix DROP TABLE IF EXISTSBruce Momjian
Patch from Joe Abbate.
2013-05-20Documentation spell checking and markup improvementsPeter Eisentraut
2013-05-19Clarify documentation of EXPLAIN (TIMING OFF) option.Tom Lane
Clarify that this option doesn't suppress measurement of the statement's total runtime. Greg Smith
2013-05-18release docs: mention PL/pgSQL as supporting event triggers in PG 9.3Bruce Momjian
2013-05-16Fix some uses of "the quick brown fox".Tom Lane
If we're going to quote a well-known pangram, we should quote it accurately. Per gripe from Thom Brown.
2013-05-14doc: Add \dm command to psql man pagePeter Eisentraut
2013-05-13doc: Fix some whitespace issues in the man pagesPeter Eisentraut
2013-05-13doc: Fix order of options on pgbench man pagePeter Eisentraut
2013-05-11Update CREATE FUNCTION documentation about argument names.Tom Lane
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.
2013-05-09Update key words table for 9.3Peter Eisentraut
2013-05-09pg_upgrade docs: give tips on automationBruce Momjian
Document that post-upgrade steps are likely to be the same for all clusters with the same DDL/schemas; this should help automated upgrades.
2013-05-08Fix walsender failure at promotion.Heikki Linnakangas
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.
2013-05-08Use the term "radix tree" instead of "suffix tree" for SP-GiST text opclass.Heikki Linnakangas
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
2013-05-07doc: Add IDs to link targets used by phpPgAdminPeter Eisentraut
Karl O. Pinc
2013-05-07Stress that backup_label file is critical in the docs.Heikki Linnakangas
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.
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
generated by cgit v1.2.3 (git 2.46.0) at 2025-11-21 23:14:43 +0000