aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Improve markup of unnest examplePeter Eisentraut2011-01-07
|
* Improve array_upper examplePeter Eisentraut2011-01-07
| | | | | The previous example didn't make it clear whether array_upper returned the last element or the index of the last element.
* Update documentation to say that \lo_import sets :LASTOID, notBruce Momjian2011-01-05
| | | | lo_insert.
* Give superusers REPLIACTION permission by defaultMagnus Hagander2011-01-05
| | | | | | | This can be overriden by using NOREPLICATION on the CREATE ROLE statement, but by default they will have it, making it backwards compatible and "less surprising" (given that superusers normally override all checks).
* Add views and functions to monitor hot standby query conflictsMagnus Hagander2011-01-03
| | | | | Add the view pg_stat_database_conflicts and a column to pg_stat_database, and the underlying functions to provide the information.
* Add missing part of replication role docsMagnus Hagander2011-01-03
| | | | Noted by Peter E.
* Implement remaining fields of information_schema.sequences viewPeter Eisentraut2011-01-02
| | | | | | | | | Add new function pg_sequence_parameters that returns a sequence's start, minimum, maximum, increment, and cycle values, and use that in the view. (bug #5662; design suggestion by Tom Lane) Also slightly adjust the view's column order and permissions after review of SQL standard.
* Basic foreign table support.Robert Haas2011-01-01
| | | | | | | | | | | Foreign tables are a core component of SQL/MED. This commit does not provide a working SQL/MED infrastructure, because foreign tables cannot yet be queried. Support for foreign table scans will need to be added in a future patch. However, this patch creates the necessary system catalog structure, syntax support, and support for ancillary operations such as COMMENT and SECURITY LABEL. Shigeru Hanada, heavily revised by Robert Haas
* Minor wordsmithing.Robert Haas2011-01-01
| | | | As suggested by Tom Lane, in response to a gripe from Leslie S Satenstein.
* Stamp copyrights for year 2011.Bruce Momjian2011-01-01
|
* Include the first valid listen address in pg_ctl to improve server startBruce Momjian2010-12-31
| | | | | "wait" detection and add postmaster start time to help determine if the postmaster is actually using the specified data directory.
* Remove tabs in SGMLPeter Eisentraut2010-12-30
|
* Doc wording improvement: taken -> acceptedBruce Momjian2010-12-29
| | | | with time zone</type>.) <type>timestamptz</type> is accepted as an
* Support unlogged tables.Robert Haas2010-12-29
| | | | | | | The contents of an unlogged table are WAL-logged; thus, they are not available on standby servers and are truncated whenever the database system enters recovery. Indexes on unlogged tables are also unlogged. Unlogged GiST indexes are not currently supported.
* Add REPLICATION privilege for ROLEsMagnus Hagander2010-12-29
| | | | | | | | | | | This privilege is required to do Streaming Replication, instead of superuser, making it possible to set up a SR slave that doesn't have write permissions on the master. Superuser privileges do NOT override this check, so in order to use the default superuser account for replication it must be explicitly granted the REPLICATION permissions. This is backwards incompatible change, in the interest of higher default security.
* Reclassify DEFAULT as a column_constraint item in the CREATE TABLE syntax.Tom Lane2010-12-28
| | | | | | | | | | | | | | This is how it was documented originally, but several years ago somebody decided that DEFAULT isn't a type of constraint. Well, the grammar thinks it is. The documentation was wrong in two ways: it alleged that DEFAULT had to appear before any other kind of constraint, and it alleged that you can't prefix a DEFAULT clause with a "CONSTRAINT name" clause, when in fact you can. (The latter behavior probably isn't SQL-standard, but our grammar has always allowed it.) This patch responds to Fujii Masao's observation that the ALTER TABLE documentation mistakenly implied that you couldn't include DEFAULT in ALTER TABLE ADD COLUMN; though this isn't the way he proposed fixing it.
* No release notes update, just advance the dateREL9_1_ALPHA3Peter Eisentraut2010-12-28
|
* Fix ill-advised placement of PGRES_COPY_BOTH enum value.Tom Lane2010-12-28
| | | | | It must be added at the end of the ExecStatusType enum to avoid ABI breakage compared to previous libpq versions. Noted by Magnus.
* Fix list of functions that are restricted to superusersMagnus Hagander2010-12-28
| | | | | Move the list of what's restricted to superusers into the table itself, so it doesn't get missed again.
* Update SGML docs describing the contents of the postmaster.pid file,Bruce Momjian2010-12-27
| | | | per change to the file for pg_ctl.
* Break up long line, per Leslie S Satenstein.Alvaro Herrera2010-12-27
|
* Corrections to patch adding SQL/MED error codes.Robert Haas2010-12-26
| | | | | | | My previous commit, 85cff3ce7f360d139d87aee836d75a6202fee066 on 2010-12-25, failed to update errcodes.sgml or plerrcodes.h. This patch corrects that oversight, per a gripe from Tom Lane, and also corrects a typographical error.
* Correct spelling: longjump() -> longjmp().Robert Haas2010-12-24
|
* Fix grammarPeter Eisentraut2010-12-24
|
* Improve "pg_ctl -w start" server detection by writing the postmasterBruce Momjian2010-12-24
| | | | | port and socket directory into postmaster.pid, and have pg_ctl read from that file, for use by PQping().
* Move the documentation of --no-security-label to a more sensible placePeter Eisentraut2010-12-24
| | | | | The order on the pg_dump/pg_dumpall man pages is not very strict, but surely putting it under connection options was wrong.
* Release notes for 9.1alpha3Peter Eisentraut2010-12-24
|
* Document pg_dump(all) --no-security-label instead of --security-label.Robert Haas2010-12-23
| | | | The former is the option actually supported by these commands.
* Rewrite the GiST insertion logic so that we don't need the post-recoveryHeikki Linnakangas2010-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cleanup stage to finish incomplete inserts or splits anymore. There was two reasons for the cleanup step: 1. When a new tuple was inserted to a leaf page, the downlink in the parent needed to be updated to contain (ie. to be consistent with) the new key. Updating the parent in turn might require recursively updating the parent of the parent. We now handle that by updating the parent while traversing down the tree, so that when we insert the leaf tuple, all the parents are already consistent with the new key, and the tree is consistent at every step. 2. When a page is split, we need to insert the downlink for the new right page(s), and update the downlink for the original page to not include keys that moved to the right page(s). We now handle that by setting a new flag, F_FOLLOW_RIGHT, on the non-rightmost pages in the split. When that flag is set, scans always follow the rightlink, regardless of the NSN mechanism used to detect concurrent page splits. That way the tree is consistent right after split, even though the downlink is still missing. This is very similar to the way B-tree splits are handled. When the downlink is inserted in the parent, the flag is cleared. To keep the insertion algorithm simple, when an insertion sees an incomplete split, indicated by the F_FOLLOW_RIGHT flag, it finishes the split before doing anything else. These changes allow removing the whole "invalid tuple" mechanism, but I retained the scan code to still follow invalid tuples correctly. While we don't create any such tuples anymore, we want to handle them gracefully in case you pg_upgrade a GiST index that has them. If we encounter any on an insert, though, we just throw an error saying that you need to REINDEX. The issue that got me into doing this is that if you did a checkpoint while an insert or split was in progress, and the checkpoint finishes quickly so that there is no WAL record related to the insert between RedoRecPtr and the checkpoint record, recovery from that checkpoint would not know to finish the incomplete insert. IOW, we have the same issue we solved with the rm_safe_restartpoint mechanism during normal operation too. It's highly unlikely to happen in practice, and this fix is far too large to backpatch, so we're just going to live with in previous versions, but this refactoring fixes it going forward. With this patch, you don't get the annoying 'index "FOO" needs VACUUM or REINDEX to finish crash recovery' notices anymore if you crash at an unfortunate moment.
* Document that BBU's do not allow partial page writes to be safely turnedBruce Momjian2010-12-22
| | | | | | off unless they guarantee that all writes to the BBU arrive in 8kB chunks. Per discussion with Greg Smith
* Typo fix.Robert Haas2010-12-22
| | | | Noted by Thom Brown.
* Wording improvements for pg_ctl manual page.Bruce Momjian2010-12-22
|
* Add PQlibVersion() function to libpqMagnus Hagander2010-12-22
| | | | | | | | | This function is like the PQserverVersion() function except it returns the version of libpq, making it possible for a client program or driver to determine which version of libpq is in use at runtime, and not just at link time. Suggested by Harald Armin Massa and several others.
* Fix typoAlvaro Herrera2010-12-20
| | | | Jaime Casanova
* Support for collecting crash dumps on WindowsMagnus Hagander2010-12-19
| | | | | | | | | | Add support for collecting "minidump" style crash dumps on Windows, by setting up an exception handling filter. Crash dumps will be generated in PGDATA/crashdumps if the directory is created (the existance of the directory is used as on/off switch for the generation of the dumps). Craig Ringer and Magnus Hagander
* Waiting for complete startup is now a well-defined operation.Robert Haas2010-12-16
| | | | Per report from Fujii Masao, and subsequent discussion.
* Some copy editing of pg_read_binary_file() patch.Robert Haas2010-12-15
|
* Document timestamptz a little better.Robert Haas2010-12-15
|
* Add pg_read_binary_file() and whole-file-at-once versions of pg_read_file().Itagaki Takahiro2010-12-16
| | | | | | | One of the usages of the binary version is to read files in a different encoding from the server encoding. Dimitri Fontaine and Itagaki Takahiro.
* Use "upgrade" in preference over "migrate" in pg_upgrade messages andBruce Momjian2010-12-15
| | | | documentation. (Many were left over from the old pg_migrator naming.)
* Update release notes for releases 9.0.2, 8.4.6, 8.3.13, 8.2.19, and 8.1.23.Tom Lane2010-12-13
|
* Remove recently reintroduced CVS keywordPeter Eisentraut2010-12-13
|
* Document replacement of pg_class.relistemp with relpersistence.Robert Haas2010-12-13
| | | | Noted by Tom Lane.
* Allow bidirectional copy messages in streaming replication mode.Robert Haas2010-12-11
| | | | Fujii Masao. Review by Alvaro Herrera, Tom Lane, and myself.
* Minor documentation cleanup.Robert Haas2010-12-10
| | | | Fujii Masao
* Force default wal_sync_method to be fdatasync on Linux.Tom Lane2010-12-08
| | | | | | | | | | | | | | | | | | | | | | | Recent versions of the Linux system header files cause xlogdefs.h to believe that open_datasync should be the default sync method, whereas formerly fdatasync was the default on Linux. open_datasync is a bad choice, first because it doesn't actually outperform fdatasync (in fact the reverse), and second because we try to use O_DIRECT with it, causing failures on certain filesystems (e.g., ext4 with data=journal option). This part of the patch is largely per a proposal from Marti Raudsepp. More extensive changes are likely to follow in HEAD, but this is as much change as we want to back-patch. Also clean up confusing code and incorrect documentation surrounding the fsync_writethrough option. Those changes shouldn't result in any actual behavioral change, but I chose to back-patch them anyway to keep the branches looking similar in this area. In 9.0 and HEAD, also do some copy-editing on the WAL Reliability documentation section. Back-patch to all supported branches, since any of them might get used on modern Linux versions.
* Optimize commit_siblings in two ways to improve group commit.Simon Riggs2010-12-08
| | | | | | | | First, avoid scanning the whole ProcArray once we know there are at least commit_siblings active; second, skip the check altogether if commit_siblings = 0. Greg Smith
* Add KNNGIST support to contrib/pg_trgm.Tom Lane2010-12-04
| | | | Teodor Sigaev, with some revision by Tom
* Add external documentation for KNNGIST.Tom Lane2010-12-03
|
* Clarify that LOCK TABLE requires a table-level privilege.Robert Haas2010-12-03
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-07 20:49:08 +0000