aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* New autovacuum_work_mem parameterSimon Riggs2013-12-12
| | | | | | | If autovacuum_work_mem is set, autovacuum workers now use this parameter in preference to maintenance_work_mem. Peter Geoghegan
* Allow time delayed standbys and recoverySimon Riggs2013-12-12
| | | | | | | | | Set min_recovery_apply_delay to force a delay in recovery apply for commit and restore point WAL records. Other records are replayed immediately. Delay is measured between WAL record time and local standby time. Robert Haas, Fabrízio de Royes Mello and Simon Riggs Detailed review by Mitsumasa Kondo
* Display old and new values in pg_resetxlog -n output.Heikki Linnakangas2013-12-12
| | | | | | For extra clarity. Rajeev Rastogi, reviewed by Amit Kapila
* PL/Perl: Add event trigger supportPeter Eisentraut2013-12-11
| | | | From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
* Add a new option, -g, to createuser, to add membership in a role.Robert Haas2013-12-11
| | | | | Chistopher Browne, reviewed by Sameer Thakur, Amit Kapila, and Peter Eisentraut.
* doc: Fix DocBook table column count declarationPeter Eisentraut2013-12-10
| | | | This was broken in d6464fdc0a591662e5e5ee1b0303932e89cb027c.
* Add new wal_level, logical, sufficient for logical decoding.Robert Haas2013-12-10
| | | | | | | | | | | | | | | | | | | | | | | When wal_level=logical, we'll log columns from the old tuple as configured by the REPLICA IDENTITY facility added in commit 07cacba983ef79be4a84fcd0e0ca3b5fcb85dd65. This makes it possible a properly-configured logical replication solution to correctly follow table updates even if they change the chosen key columns, or, with REPLICA IDENTITY FULL, even if the table has no key at all. Note that updates which do not modify the replica identity column won't log anything extra, making the choice of a good key (i.e. one that will rarely be changed) important to performance when wal_level=logical is configured. Each insert, update, or delete to a catalog table will also log the CMIN and/or CMAX values of stamped by the current transaction. This is necessary because logical decoding will require access to historical snapshots of the catalog in order to decode some data types, and the CMIN/CMAX values that we may need in order to judge row visibility may have been overwritten by the time we need them. Andres Freund, reviewed in various versions by myself, Heikki Linnakangas, KONDO Mitsumasa, and many others.
* Rename TABLE() to ROWS FROM().Noah Misch2013-12-10
| | | | | | | SQL-standard TABLE() is a subset of UNNEST(); they deal with arrays and other collection types. This feature, however, deals with set-returning functions. Use a different syntax for this feature to keep open the possibility of implementing the standard TABLE().
* pgcrypto docs: update cpu type used in duration testingBruce Momjian2013-12-09
|
* pgcrypto docs: update encryption timings and add relative timesBruce Momjian2013-12-09
| | | | Miles Elam
* Fix a couple of typosMagnus Hagander2013-12-07
| | | | Noted by Peter Geoghegan
* SSL: Support ECDH key exchangePeter Eisentraut2013-12-07
| | | | | | | | | | | | | | | | | This sets up ECDH key exchange, when compiling against OpenSSL that supports EC. Then the ECDHE-RSA and ECDHE-ECDSA cipher suites can be used for SSL connections. The latter one means that EC keys are now usable. The reason for EC key exchange is that it's faster than DHE and it allows to go to higher security levels where RSA will be horribly slow. There is also new GUC option ssl_ecdh_curve that specifies the curve name used for ECDH. It defaults to "prime256v1", which is the most common curve in use in HTTPS. From: Marko Kreen <markokr@gmail.com> Reviewed-by: Adrian Klaver <adrian.klaver@gmail.com>
* Expose qurey ID in pg_stat_statements view.Fujii Masao2013-12-08
| | | | | | | The query ID is the internal hash identifier of the statement, and was not available in pg_stat_statements view so far. Daniel Farina, Sameer Thakur and Peter Geoghegan, reviewed by me.
* SSL: Add configuration option to prefer server cipher orderPeter Eisentraut2013-12-07
| | | | | | | | | | | | | | | By default, OpenSSL (and SSL/TLS in general) lets the client cipher order take priority. This is OK for browsers where the ciphers were tuned, but few PostgreSQL client libraries make the cipher order configurable. So it makes sense to have the cipher order in postgresql.conf take priority over client defaults. This patch adds the setting "ssl_prefer_server_ciphers" that can be turned on so that server cipher order is preferred. Per discussion, this now defaults to on. From: Marko Kreen <markokr@gmail.com> Reviewed-by: Adrian Klaver <adrian.klaver@gmail.com>
* docs: update partition encryption optionsBruce Momjian2013-12-06
| | | | Text from Adam Vande More
* docs: clarify SSL certificate authority chain docsBruce Momjian2013-12-06
| | | | | Previously, the requirements of how intermediate certificates were handled and their chain to root certificates was unclear.
* doc: split long query into multiple linesBruce Momjian2013-12-04
| | | | Report from Erik Rijkers
* libpq: change PQconndefaults() to ignore invalid service filesBruce Momjian2013-12-03
| | | | | | | | Previously missing or invalid service files returned NULL. Also fix pg_upgrade to report "out of memory" for a null return from PQconndefaults(). Patch by Steve Singer, rewritten by me
* doc: Refine documentation about recovery command exist statusPeter Eisentraut2013-12-02
| | | | | | | Add more documentation about how different exit codes and signals are handled in each case. Reviewed-by: Peter Geoghegan <pg@heroku.com>
* Update release notes for 9.3.2, 9.2.6, 9.1.11, 9.0.15, 8.4.19.Tom Lane2013-12-02
|
* doc: update wording of ineffective SET and ABORT commandsBruce Momjian2013-12-02
| | | | Wording by Alvaro Herrera
* Improve draft release notes.Tom Lane2013-12-02
| | | | | Per suggestions from Andres Freund. Also fix spelling of Sergey Burladyan's name.
* Draft release notes for 9.3.2.Tom Lane2013-12-01
| | | | | | I'm putting these up for review before I start to extract the relevant subsets for the older branches. It'll be easier to make any suggested wording improvements at this stage.
* doc: Disable preface.autolabel in XSLTPeter Eisentraut2013-12-01
| | | | The makes the output more consistent with the existing DSSSL setup.
* Editorial corrections to the October 2013 minor-release notes.Tom Lane2013-11-30
| | | | | | | | | | | This is mostly to fix incorrect migration instructions: since the preceding minor releases advised reindexing some GIST indexes, it's important that we back-link to that advice rather than earlier instances. Also improve some bug descriptions and fix a few typos. No back-patch yet; these files will get copied into the back branches later in the release process.
* doc: Simplify handling of variablelists in XSLT buildPeter Eisentraut2013-11-29
| | | | | | The previously used custom template is no longer necessary because parameters provided by the standard style sheet can achieve the same outcome.
* doc: Enhance documentation of ssl_ciphers setting a bitPeter Eisentraut2013-11-29
|
* doc: Allow selecting web site CSS style sheet in XSLT HTML buildPeter Eisentraut2013-11-28
|
* doc: Set chunk.first.sections in XSLT, for consistency with DSSSL outputPeter Eisentraut2013-11-27
|
* pg_buffercache docs: adjust order of fieldsBruce Momjian2013-11-27
| | | | | | Adjust order of fields to match view order. Jaime Casanova
* doc: Put data types in alphabetical orderPeter Eisentraut2013-11-27
| | | | From: Andreas Karlsson <andreas@proxel.se>
* Minor correction of READ COMMITTED isolation level docs.Kevin Grittner2013-11-27
| | | | Per report from AK
* Documentation fix for ecpg.Michael Meskes2013-11-27
| | | | The latest fixes removed a limitation that was still in the docs, so Zoltan updated the docs, too.
* Add --xlogdir option to pg_basebackup, for specifying the pg_xlog directory.Fujii Masao2013-11-27
| | | | Haribabu kommi, slightly modified by me.
* Fix typo in release note.Fujii Masao2013-11-27
| | | | | | Backpatch to 9.1. Josh Kupershmidt
* Implement information_schema.parameters.parameter_default columnPeter Eisentraut2013-11-26
| | | | | | Reviewed-by: Ali Dar <ali.munir.dar@gmail.com> Reviewed-by: Amit Khandekar <amit.khandekar@enterprisedb.com> Reviewed-by: Rodolfo Campero <rodolfo.campero@anachronics.com>
* doc: Add id to index in XSLT buildPeter Eisentraut2013-11-26
| | | | | That way, the HTML file name of the index will be the same as currently for the DSSSL build.
* Change SET LOCAL/CONSTRAINTS/TRANSACTION and ABORT behaviorBruce Momjian2013-11-25
| | | | | | | Change SET LOCAL/CONSTRAINTS/TRANSACTION behavior outside of a transaction block from error (post-9.3) to warning. (Was nothing in <= 9.3.) Also change ABORT outside of a transaction block from notice to warning.
* More improvement to comment parsing in ecpg.Michael Meskes2013-11-25
| | | | | | ECPG is not supposed to allow and output nested comments in C. These comments are only allowed in the SQL parts and must not be written into the C file. Also the different handling of different comments is documented.
* PL/Tcl: Add event trigger supportPeter Eisentraut2013-11-23
| | | | From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
* Support multi-argument UNNEST(), and TABLE() syntax for multiple functions.Tom Lane2013-11-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds the ability to write TABLE( function1(), function2(), ...) as a single FROM-clause entry. The result is the concatenation of the first row from each function, followed by the second row from each function, etc; with NULLs inserted if any function produces fewer rows than others. This is believed to be a much more useful behavior than what Postgres currently does with multiple SRFs in a SELECT list. This syntax also provides a reasonable way to combine use of column definition lists with WITH ORDINALITY: put the column definition list inside TABLE(), where it's clear that it doesn't control the ordinality column as well. Also implement SQL-compliant multiple-argument UNNEST(), by turning UNNEST(a,b,c) into TABLE(unnest(a), unnest(b), unnest(c)). The SQL standard specifies TABLE() with only a single function, not multiple functions, and it seems to require an implicit UNNEST() which is not what this patch does. There may be something wrong with that reading of the spec, though, because if it's right then the spec's TABLE() is just a pointless alternative spelling of UNNEST(). After further review of that, we might choose to adopt a different syntax for what this patch does, but in any case this functionality seems clearly worthwhile. Andrew Gierth, reviewed by Zoltán Böszörményi and Heikki Linnakangas, and significantly revised by me
* docs: update page format to specify page checksum fieldBruce Momjian2013-11-19
| | | | | | Backpatch to 9.3 Per report from Steffen Hildebrandt
* Add make_date() and make_time() functions.Tom Lane2013-11-17
| | | | Pavel Stehule, reviewed by Jeevan Chalke and Atri Sharma
* Allow aggregates to provide estimates of their transition state data size.Tom Lane2013-11-16
| | | | | | | | | | | | | | | | | | | | Formerly the planner had a hard-wired rule of thumb for guessing the amount of space consumed by an aggregate function's transition state data. This estimate is critical to deciding whether it's OK to use hash aggregation, and in many situations the built-in estimate isn't very good. This patch adds a column to pg_aggregate wherein a per-aggregate estimate can be provided, overriding the planner's default, and infrastructure for setting the column via CREATE AGGREGATE. It may be that additional smarts will be required in future, perhaps even a per-aggregate estimation function. But this is already a step forward. This is extracted from a larger patch to improve the performance of numeric and int8 aggregates. I (tgl) thought it was worth reviewing and committing this infrastructure separately. In this commit, all built-in aggregates are given aggtransspace = 0, so no behavior should change. Hadi Moshayedi, reviewed by Pavel Stehule and Tomas Vondra
* doc: Restore proper alphabetical order.Robert Haas2013-11-15
| | | | Colin 't Hart
* Clarify CREATE FUNCTION documentation about handling of typmods.Tom Lane2013-11-13
| | | | | The previous text was a bit misleading, as well as unnecessarily vague about what information would be discarded. Per gripe from Craig Skinner.
* docs: clarify MVCC introduction to allow for per-statement snapshotsBruce Momjian2013-11-13
|
* doc: Fix typo.Robert Haas2013-11-12
| | | | Reported by Thom Brown.
* Fix whitespace issues found by git diff --check, add gitattributesPeter Eisentraut2013-11-10
| | | | | Set per file type attributes in .gitattributes to fine-tune whitespace checks. With the associated cleanups, the tree is now clean for git
* doc: Clarify under what circumstances pg_dump needs superuser access.Robert Haas2013-11-08
| | | | Inspired by, but different from, a patch from Ivan Lezhnjov IV
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-19 17:38:18 +0000