aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Remove more SGML tabs.Bruce Momjian2011-02-09
|
* Remove tabs in SGML file.Bruce Momjian2011-02-09
|
* Implement NOWAIT option for BASE_BACKUP commandMagnus Hagander2011-02-09
| | | | | | | | | | Specifying this option makes the server not wait for the xlog to be archived, or emit a warning that it can't, instead leaving the responsibility with the client. This is useful when the log is being streamed using the streaming protocol in parallel with the backup, without having log archiving enabled.
* Core support for "extensions", which are packages of SQL objects.Tom Lane2011-02-08
| | | | | | | | | | | | | This patch adds the server infrastructure to support extensions. There is still one significant loose end, namely how to make it play nice with pg_upgrade, so I am not yet committing the changes that would make all the contrib modules depend on this feature. In passing, fix a disturbingly large amount of breakage in AlterObjectNamespace() and callers. Dimitri Fontaine, reviewed by Anssi Kääriäinen, Itagaki Takahiro, Tom Lane, and numerous others
* Per-column collation supportPeter Eisentraut2011-02-08
| | | | | | | | This adds collation support for columns and domains, a COLLATE clause to override it per expression, and B-tree index support. Peter Eisentraut reviewed by Pavel Stehule, Itagaki Takahiro, Robert Haas, Noah Misch
* Fix typo, by Kevin Grittner.Heikki Linnakangas2011-02-08
|
* Named restore points in recovery. Users can record named points, thenSimon Riggs2011-02-08
| | | | | | | new recovery.conf parameter recovery_target_name allows PITR to specify named points as recovery targets. Jaime Casanova, reviewed by Euler Taveira de Oliveira, plus minor edits
* Basic Recovery Control functions for use in Hot Standby. Pause, Resume,Simon Riggs2011-02-08
| | | | | | | Status check functions only. Also, new recovery.conf parameter to pause_at_recovery_target, default on. Simon Riggs, reviewed by Fujii Masao
* Extend ALTER TABLE to allow Foreign Keys to be added without initial validation.Simon Riggs2011-02-08
| | | | | | | | | FK constraints that are marked NOT VALID may later be VALIDATED, which uses an ShareUpdateExclusiveLock on constraint table and RowShareLock on referenced table. Significantly reduces lock strength and duration when adding FKs. New state visible from psql. Simon Riggs, with reviews from Marko Tiikkaja and Robert Haas
* Fix copy-pasto in description of pg_serial, and silence compiler warningHeikki Linnakangas2011-02-08
| | | | about uninitialized field you get on some compilers.
* Avoid having autovacuum workers wait for relation locks.Robert Haas2011-02-07
| | | | | | | | | | | | Waiting for relation locks can lead to starvation - it pins down an autovacuum worker for as long as the lock is held. But if we're doing an anti-wraparound vacuum, then we still wait; maintenance can no longer be put off. To assist with troubleshooting, if log_autovacuum_min_duration >= 0, we log whenever an autovacuum or autoanalyze is skipped for this reason. Per a gripe by Josh Berkus, and ensuing discussion.
* Oops, forgot to bump catversion in the Serializable Snapshot Isolation patch.Heikki Linnakangas2011-02-08
| | | | | I thought we didn't need that, but then I remembered that it added a new SLRU subdirectory, pg_serial. While we're at it, document what pg_serial is.
* Implement genuine serializable isolation level.Heikki Linnakangas2011-02-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Until now, our Serializable mode has in fact been what's called Snapshot Isolation, which allows some anomalies that could not occur in any serialized ordering of the transactions. This patch fixes that using a method called Serializable Snapshot Isolation, based on research papers by Michael J. Cahill (see README-SSI for full references). In Serializable Snapshot Isolation, transactions run like they do in Snapshot Isolation, but a predicate lock manager observes the reads and writes performed and aborts transactions if it detects that an anomaly might occur. This method produces some false positives, ie. it sometimes aborts transactions even though there is no anomaly. To track reads we implement predicate locking, see storage/lmgr/predicate.c. Whenever a tuple is read, a predicate lock is acquired on the tuple. Shared memory is finite, so when a transaction takes many tuple-level locks on a page, the locks are promoted to a single page-level lock, and further to a single relation level lock if necessary. To lock key values with no matching tuple, a sequential scan always takes a relation-level lock, and an index scan acquires a page-level lock that covers the search key, whether or not there are any matching keys at the moment. A predicate lock doesn't conflict with any regular locks or with another predicate locks in the normal sense. They're only used by the predicate lock manager to detect the danger of anomalies. Only serializable transactions participate in predicate locking, so there should be no extra overhead for for other transactions. Predicate locks can't be released at commit, but must be remembered until all the transactions that overlapped with it have completed. That means that we need to remember an unbounded amount of predicate locks, so we apply a lossy but conservative method of tracking locks for committed transactions. If we run short of shared memory, we overflow to a new "pg_serial" SLRU pool. We don't currently allow Serializable transactions in Hot Standby mode. That would be hard, because even read-only transactions can cause anomalies that wouldn't otherwise occur. Serializable isolation mode now means the new fully serializable level. Repeatable Read gives you the old Snapshot Isolation level that we have always had. Kevin Grittner and Dan Ports, reviewed by Jeff Davis, Heikki Linnakangas and Anssi Kääriäinen
* remove tags.Bruce Momjian2011-02-06
|
* Force strings passed to and from plperl to be in UTF8 encoding.Andrew Dunstan2011-02-06
| | | | | | | | | | | String are converted to UTF8 on the way into perl and to the database encoding on the way back. This avoids a number of observed anomalies, and ensures Perl a consistent view of the world. Some minor code cleanups are also accomplished. Alex Hunsaker, reviewed by Andy Colson.
* Adjust libpq docs to be clearer about 'hostaddr' usage by rewording andBruce Momjian2011-02-06
| | | | using an itemized list.
* Add doc comment that installation.sgml can't use xrefs.Bruce Momjian2011-02-04
|
* In docs, move PQrequestCancel() deprecation mention up to match otherBruce Momjian2011-02-04
| | | | libpq doc mentions.
* Update ALTER TABLE docs to mention using VACUUM FULL for rewrites.Robert Haas2011-02-04
| | | | | | | Remove the claim that ALTER TABLE .. SET DATA TYPE is the fastest way of rewriting a table, since it no longer is. Noah Misch and Robert Haas, based on a suggestion from Tom Lane.
* Attempt to un-break the documentation build againMagnus Hagander2011-02-04
| | | | | Another case of <xref linkend> in the documentation that builds INSTALL, which is not allowed.
* Avoid maintaining three separate copies of the error codes list.Robert Haas2011-02-03
| | | | | | | | src/pl/plpgsql/src/plerrcodes.h, src/include/utils/errcodes.h, and a big chunk of errcodes.sgml are now automatically generated from a single file, src/backend/utils/errcodes.txt. Jan Urbański, reviewed by Tom Lane.
* ALTER TABLE sometimes takes only ShareUpdateExclusiveLock.Robert Haas2011-02-03
| | | | Along the way, be more consistent about the wording we use here.
* In docs, PL is Procedural Language, not Programming Language.Bruce Momjian2011-02-03
| | | | Satoshi Nagayasu
* Include more status information in walsender resultsMagnus Hagander2011-02-03
| | | | | | Add the current xlog insert location to the response of IDENTIFY_SYSTEM, and adds result sets containing start and stop location of backups to BASE_BACKUP responses.
* Fix typo.Magnus Hagander2011-02-03
| | | | Thom Brown
* Further sepgsql documentation cleanup.Robert Haas2011-02-03
|
* sepgsql doc fixRobert Haas2011-02-02
| | | | KaiGai Kohei
* Log restartpoints in the same fashion as checkpoints.Robert Haas2011-02-02
| | | | | | | | | Prior to 9.0, restartpoints never created, deleted, or recycled WAL files, but now they can. This code makes log_checkpoints treat checkpoints and restartpoints symmetrically. It also adjusts up the documentation of the parameter to mention restartpoints. Fujii Masao. Docs by me, as suggested by Itagaki Takahiro.
* Mark all GUC variables with <varname> markup, rather than <literal>.Bruce Momjian2011-02-02
|
* Wrap PL/Python SPI calls into subtransactionsPeter Eisentraut2011-02-02
| | | | | | | | | | | This allows the language-specific try/catch construct to catch and handle exceptions arising from SPI calls, matching the behavior of other PLs. As an additional bonus you no longer get all the ugly "unrecognized error in PLy_spi_execute_query" errors. Jan Urbański, reviewed by Steve Singer
* Document that CREATE VIEW that uses "*" for the column list will notBruce Momjian2011-02-01
| | | | auto-add columns later added to the base table.
* Properly capitalize hyphenated words in documentation titles.Bruce Momjian2011-02-01
|
* Clarify documentation to state that "zero_damaged_pages" does not forceBruce Momjian2011-02-01
| | | | | data to disk, so the table or index should be recreated before the parameter is turned off again.
* Document that effective cache size does not assume data remains in theBruce Momjian2011-02-01
| | | | cache between queries.
* Document that Slony can do upgrades easier _because_ it supportsBruce Momjian2011-02-01
| | | | replication between different Postgres major versions.
* Clarify pg_upgrade install instructions, per suggestion from Robert Haas.Bruce Momjian2011-02-01
|
* Add missing period "." in pg_upgrade documentation.Bruce Momjian2011-02-01
|
* Re-classify ERRCODE_DATABASE_DROPPED to 57P04Simon Riggs2011-02-01
|
* Add a link from client_encoding parameter to the list of character setsItagaki Takahiro2011-02-01
| | | | | | in documentation. Thom Brown
* Improve docs for pg_authid encryption description with better markup andBruce Momjian2011-01-31
| | | | a mention of unencrypted passwords.
* In pg_authid.rolpassword docs, make "md5" appear as a literal.Bruce Momjian2011-01-31
|
* Support LIKE and ILIKE index searches via contrib/pg_trgm indexes.Tom Lane2011-01-31
| | | | | | | | | | Unlike Btree-based LIKE optimization, this works for non-left-anchored search patterns. The effectiveness of the search depends on how many trigrams can be extracted from the pattern. (The worst case, with no trigrams, degrades to a full-table scan, so this isn't a panacea. But it can be very useful.) Alexander Korotkov, reviewed by Jan Urbanski
* Create new errcode for recovery conflict caused by db drop on master.Simon Riggs2011-02-01
| | | | | | | | | Previously reported as ERRCODE_ADMIN_SHUTDOWN, this case is now reported as ERRCODE_T_R_DATABASE_DROPPED. No message text change. Unlikely to happen on most servers, so low impact change to allow session poolers to correctly handle this situation. Tatsuo Ishii, edits by me, review by Robert Haas
* Remove spurious word, spotted by Thom Brown.Heikki Linnakangas2011-01-31
|
* Update pg_upgrade docs to mention its use in a less risk-warning way,Bruce Momjian2011-01-31
| | | | | and update the pg_upgrade docs to mention its reliance on no changes to the storage format (the later based on Robert Haas's patch).
* Fix SGML markup for upgrade doc addition.Bruce Momjian2011-01-31
|
* Update docs on building for Windows to accomodate current reality.Andrew Dunstan2011-01-31
| | | | | | | | | | Document how to build 64 bit Windows binaries using the MinGW64 tool set. Remove recommendation against using Mingw as a build platform. Be more specific about when Cygwin is useful and when it's not, in particular note its usefulness for running psql, and add a note about building on Cygwin in non-C locales. Per recent discussions.
* Move upgrade instructions into its own section under "Server Setup andBruce Momjian2011-01-31
| | | | | | Operation", merged from upgrade sections in "Installation from Source Code" and "Backup and Restore". This now gives a single place for all upgrade information.
* Support multiple concurrent pg_basebackup backups.Heikki Linnakangas2011-01-31
| | | | | | | | | With this patch, pg_basebackup doesn't write a backup_label file in the data directory, so it doesn't interfere with a pg_start/stop_backup() based backup anymore. backup_label is still included in the backup, but it is injected directly into the tar stream. Heikki Linnakangas, reviewed by Fujii Masao and Magnus Hagander.
* Add option to include WAL in base backupMagnus Hagander2011-01-30
| | | | | | | | | When included, this makes the base backup a complete working "clone" of the initial database, ready to have a postmaster started against it without the need to set up any log archiving or similar. Magnus Hagander, reviewed by Fujii Masao and Heikki Linnakangas
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-06 09:52:02 +0000