aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Properly capitalize documentation headings; some only had initial-wordBruce Momjian2011-01-29
| | | | capitalization.
* Make installation.sgml build standalone again.Tom Lane2011-01-29
| | | | | | We must not try to link to sections that aren't part of the standalone "make INSTALL" build. Corrects build failure introduced in commit 159e3d86292cfec2a2828f9f69ac7a6cb1be242d.
* Copy-edit a paragraph in the contrib/seg documentation.Tom Lane2011-01-28
| | | | | | Although this improves the style, an ulterior motive is to keep the two table links from breaking across lines in PDF output, per complaint from Josh Kupershmidt.
* Rephrase pg_conversion description to avoid splitting link across page.Tom Lane2011-01-27
| | | | | | | | | | | The link to the CREATE CONVERSION manual page was split across a page boundary in the PDF output, leading to "\pdfendlink ended up in different nesting level than \pdfstartlink" error while building PDFs. It wouldn't be worth changing text that's undergoing active editing to avoid this, since other editing might result in moving the link away from the page end anyway. But this paragraph has been static for a long time, so might as well fix it to prevent it from being an issue in future.
* Update release notes.Tom Lane2011-01-27
| | | | Security: CVE-2010-4015
* Update release notes for releases 9.0.3, 8.4.7, 8.3.14, and 8.2.20.Tom Lane2011-01-27
|
* Improve grammar and spelling in durability discussion.Tom Lane2011-01-27
|
* Update non-durable docs about non-synchronous-commit allowingBruce Momjian2011-01-27
| | | | transaction loss for a _database_ crash.
* Restructure streaming docs so streaming seems more integrated in theBruce Momjian2011-01-26
| | | | paragraphs, per suggestion from Dan Birken.
* Update contrib documention mentions to point to actual documentationBruce Momjian2011-01-26
| | | | | | sections, rather than just calling it "/contrib/module_name". Also update pg_test_fsync build instructions now that it is in /contrib.
* Update sync commit performance documentation to be consistent with otherBruce Momjian2011-01-26
| | | | non-durable items, per Robert Haas.
* Make 'on' uppercase in a sql example.Itagaki Takahiro2011-01-26
|
* Update warning about synchronous-commit durability, per suggestion fromBruce Momjian2011-01-25
| | | | Robvert Haas.
* Correct ALTER TYPE -> SET DATA TYPE in ALTER TABLE documentation.Robert Haas2011-01-25
| | | | | | | The latter is the correct name of the operation to change the data type of a column. Noah Misch
* Remove old claim that ExclusiveLock is sometimes taken on system catalogs.Tom Lane2011-01-25
| | | | | | We used to do that on pg_listener, but pg_listener is no more. Also add a bit more documentation for ShareRowExclusive mode.
* Fix thinko in ALTER FOREIGN TABLE documentation.Robert Haas2011-01-25
| | | | Noah Misch
* Replace pg_class.relhasexclusion with pg_index.indisexclusion.Tom Lane2011-01-25
| | | | | | | There isn't any need to track this state on a table-wide basis, and trying to do so introduces undesirable semantic fuzziness. Move the flag to pg_index, where it clearly describes just a single index and can be immutable after index creation.
* Implement ALTER TABLE ADD UNIQUE/PRIMARY KEY USING INDEX.Tom Lane2011-01-25
| | | | | | | | | | | | | | | | | | | This feature allows a unique or pkey constraint to be created using an already-existing unique index. While the constraint isn't very functionally different from the bare index, it's nice to be able to do that for documentation purposes. The main advantage over just issuing a plain ALTER TABLE ADD UNIQUE/PRIMARY KEY is that the index can be created with CREATE INDEX CONCURRENTLY, so that there is not a long interval where the table is locked against updates. On the way, refactor some of the code in DefineIndex() and index_create() so that we don't have to pass through those functions in order to create the index constraint's catalog entries. Also, in parse_utilcmd.c, pass around the ParseState pointer in struct CreateStmtContext to save on notation, and add error location pointers to some error reports that didn't have one before. Gurjeet Singh, reviewed by Steve Singer and Tom Lane
* More documentation cleanup for sepgsql.Robert Haas2011-01-24
| | | | Thom Brown and Robert Haas
* First round of cleanup of sepgsql code and documentation.Robert Haas2011-01-23
| | | | Robert Haas, with a few suggestions from Thom Brown
* sepgsql, an SE-Linux integration for PostgreSQLRobert Haas2011-01-23
| | | | | | | | This is still pretty rough - among other things, the documentation needs work, and the messages need a visit from the style police - but this gets the basic framework in place. KaiGai Kohei
* Add 'directory' format to pg_dump. The new directory format is compatibleHeikki Linnakangas2011-01-23
| | | | | | | with the 'tar' format, in that untarring a tar format archive produces a valid directory format archive. Joachim Wieland and Heikki Linnakangas
* Only show pg_stat_replication details to superusersMagnus Hagander2011-01-23
|
* Add pg_basebackup tool for streaming base backupsMagnus Hagander2011-01-23
| | | | | | | | | | | | | | | This tool makes it possible to do the pg_start_backup/ copy files/pg_stop_backup step in a single command. There are still some steps to be done before this is a complete backup solution, such as the ability to stream the required WAL logs, but it's still usable, and could do with some buildfarm coverage. In passing, make the checkpoint request optionally fast instead of hardcoding it. Magnus Hagander, reviewed by Fujii Masao and Dimitri Fontaine
* Allow the wal_buffers setting to be auto-tuned to a reasonable value.Tom Lane2011-01-22
| | | | | | | | | If wal_buffers is initially set to -1 (which is now the default), it's replaced by 1/32nd of shared_buffers, with a minimum of 8 (the old default) and a maximum of the XLOG segment size. The allowed range for manual settings is still from 4 up to whatever will fit in shared memory. Greg Smith, with implementation correction by me.
* Clean up pg_test_fsync commit.Tom Lane2011-01-21
| | | | | | Actually rename the program, rather than just claiming we did. Hook it into the build system. Get rid of useless dependency on libpq. Clean up #include list and messy whitespace.
* Fix broken markup, also minor copy-editing.Tom Lane2011-01-21
|
* Emphasize where OVER needs to be when using a window function.Robert Haas2011-01-21
| | | | Jeff Turner
* Update SGML docs to point to new /contrib/pg_test_fsync.Bruce Momjian2011-01-21
|
* Move test_fsync to /contrib.Bruce Momjian2011-01-21
|
* Add new psql command \dL to list languages.Robert Haas2011-01-20
| | | | | Original patch by Fernando Ike, revived by Josh Kuperschmidt, reviewed by Andreas Karlsson, and in earlier versions by Tom Lane and Peter Eisentraut.
* Document that WITH queries are also called Common Table Expressions.Robert Haas2011-01-19
| | | | Peter Geoghegan, reviewed by Stephen Frost
* Show correct datatype for pg_class.relpersistence, plus a typo fix.Tom Lane2011-01-19
| | | | Thom Brown
* In the docs, better distinguish server from client SSL settings in the ↵Bruce Momjian2011-01-17
| | | | | | | | documentation. Ray Stell Also fix some libpq title capitalization problems.
* Use a lexer and grammar for parsing walsender commandsMagnus Hagander2011-01-14
| | | | | | | | | | | Makes it easier to parse mainly the BASE_BACKUP command with it's options, and avoids having to manually deal with quoted identifiers in the label (previously broken), and makes it easier to add new commands and options in the future. In passing, refactor the case statement in the walsender to put each command in it's own function.
* Code review for postmaster.pid contents changes.Tom Lane2011-01-13
| | | | | | | | | | Fix broken test for pre-existing postmaster, caused by wrong code for appending lines to the lockfile; don't write a failed listen_address setting into the lockfile; don't arbitrarily change the location of the data directory in the lockfile compared to previous releases; provide more consistent and useful definitions of the socket path and listen_address entries; avoid assuming that pg_ctl has the same DEFAULT_PGSOCKET_DIR as the postmaster; assorted code style improvements.
* More libpq documentation adjustments from Leslie S Satenstein, reviewedBruce Momjian2011-01-13
| | | | by Robert Haas.
* Don't run regression tests in SQL_ASCII encoding by defaultPeter Eisentraut2011-01-13
| | | | | | | | Instead, run them in the encoding that the locale selects, which is more representative of real use. Also document how locale and encoding for regression test runs can be selected.
* Apply libpq documentation patches submitted by Leslie S Satenstein andBruce Momjian2011-01-12
| | | | reviewed by Robert Haas.
* Revert patch adding support for logging the current role.Robert Haas2011-01-12
| | | | | | | | This reverts commit a8a8867912c46a68c9ac14903b3dba2fab8f7097, committed by me earlier today (2011-01-12). This isn't safe inside an aborted transaction. Noted by Tom Lane.
* Add support for logging the current role.Robert Haas2011-01-12
| | | | Stephen Frost, with some editorialization by me.
* Add some subsection headingsPeter Eisentraut2011-01-11
|
* Track walsender state in shared memory and expose in pg_stat_replicationMagnus Hagander2011-01-11
|
* Typo fixMagnus Hagander2011-01-11
| | | | Josh Kupershmidt
* Backend support for streaming base backupsMagnus Hagander2011-01-10
| | | | | | | | | | | Add BASE_BACKUP command to walsender, allowing it to stream a base backup to the client (in tar format). The syntax is still far from ideal, that will be fixed in the switch to use a proper grammar for walsender. No client included yet, will come as a separate commit. Magnus Hagander and Heikki Linnakangas
* Fix assorted corner-case bugs in contrib/intarray.Tom Lane2011-01-09
| | | | | | | | | | | | | | | | | | | The array containment operators now behave per mathematical expectation for empty arrays (ie, an empty array is contained in anything). Both these operators and the query_int operators now work as expected in GiST and GIN index searches, rather than having corner cases where the index searches gave different answers. Also, fix unexpected failures where the operators would claim that an array contained nulls, when in fact there was no longer any null present (similar to bug #5784). The restriction to not have nulls is still there, as removing it would take a lot of added code complexity and probably slow things down significantly. Also, remove the arbitrary restriction to 1-D arrays; unlike the other restriction, this was buying us nothing performance-wise. Assorted cosmetic improvements and marginal performance improvements, too.
* Remove pg_am.amindexnulls.Tom Lane2011-01-08
| | | | | | | | | The only use we have had for amindexnulls is in determining whether an index is safe to cluster on; but since the addition of the amclusterable flag, that usage is pretty redundant. In passing, clean up assorted sloppiness from the last patch that touched pg_am.h: Natts_pg_am was wrong, and ambuildempty was not documented.
* Remove bogus claims regarding createuser defaults.Robert Haas2011-01-08
| | | | Josh Kupershmidt
* Fix GIN to support null keys, empty and null items, and full index scans.Tom Lane2011-01-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Per my recent proposal(s). Null key datums can now be returned by extractValue and extractQuery functions, and will be stored in the index. Also, placeholder entries are made for indexable items that are NULL or contain no keys according to extractValue. This means that the index is now always complete, having at least one entry for every indexed heap TID, and so we can get rid of the prohibition on full-index scans. A full-index scan is implemented much the same way as partial-match scans were already: we build a bitmap representing all the TIDs found in the index, and then drive the results off that. Also, introduce a concept of a "search mode" that can be requested by extractQuery when the operator requires matching to empty items (this is just as cheap as matching to a single key) or requires a full index scan (which is not so cheap, but it sure beats failing or giving wrong answers). The behavior remains backward compatible for opclasses that don't return any null keys or request a non-default search mode. Using these features, we can now make the GIN index opclass for anyarray behave in a way that matches the actual anyarray operators for &&, <@, @>, and = ... which it failed to do before in assorted corner cases. This commit fixes the core GIN code and ginarrayprocs.c, updates the documentation, and adds some simple regression test cases for the new behaviors using the array operators. The tsearch and contrib GIN opclass support functions still need to be looked over and probably fixed. Another thing I intend to fix separately is that this is pretty inefficient for cases where more than one scan condition needs a full-index search: we'll run duplicate GinScanEntrys, each one of which builds a large bitmap. There is some existing logic to merge duplicate GinScanEntrys but it needs refactoring to make it work for entries belonging to different scan keys. Note that most of gin.h has been split out into a new file gin_private.h, so that gin.h doesn't export anything that's not supposed to be used by GIN opclasses or the rest of the backend. I did quite a bit of other code beautification work as well, mostly fixing comments and choosing more appropriate names for things.
* Document pg_stat_replication, bump catversion since that was overlooked.Robert Haas2011-01-07
| | | | Itagaki Takahiro, edited by me.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-07 02:06:05 +0000