aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Improvements to the replication protocol documentation.Andres Freund2014-05-31
| | | | | | | | | Document the CREATE_REPLICATION_SLOT's output_plugin parameter; that START_REPLICATION ... LOGICAL takes parameters; that START_REPLICATION ... LOGICAL uses the same messages as ... PHYSICAL; and be more consistent with the usage of <literal/>. Michael Paquier, with some additional changes by me.
* In release notes, mention the need to initialize bgw_notify_pid.Robert Haas2014-05-29
| | | | Michael Paquier
* doc: improve markup of ssl_ecdh_curve commitBruce Momjian2014-05-28
|
* doc: improve ssl_ecdh_curve descriptionsBruce Momjian2014-05-27
| | | | Patch by Marko Kreen
* Support BSD and e2fsprogs UUID libraries alongside OSSP UUID library.Tom Lane2014-05-27
| | | | | | | | | | | | | | | | | | | Allow the contrib/uuid-ossp extension to be built atop any one of these three popular UUID libraries. (The extension's name is now arguably a misnomer, but we'll keep it the same so as not to cause unnecessary compatibility issues for users.) We would not normally consider a change like this post-beta1, but the issue has been forced by our upgrade to autoconf 2.69, whose more rigorous header checks are causing OSSP's header files to be rejected on some platforms. It's been foreseen for some time that we'd have to move away from depending on OSSP UUID due to lack of upstream maintenance, so this is a down payment on that problem. While at it, add some simple regression tests, in hopes of catching any major incompatibilities between the three implementations. Matteo Beccati, with some further hacking by me
* doc: link/caps fixes for 9.4 release notesBruce Momjian2014-05-23
| | | | Report by Tomonari Katsumata
* doc: add ALTER TABLE lock level item as major 9.4 itemBruce Momjian2014-05-21
| | | | Report by Simon Riggs
* doc: 9.4 release notes update for pg_bench line limit itemBruce Momjian2014-05-20
| | | | Report by David Johnston
* Fix typo in JSON function document.Fujii Masao2014-05-19
|
* Fix incorrect column name in pg_stat_replication document.Fujii Masao2014-05-19
| | | | Fabrízio de Royes Mello
* doc: adjust JSONB 9.4 release note itemBruce Momjian2014-05-19
| | | | Report by Andrew Dunstan
* doc: 9.4 release note adjustementsBruce Momjian2014-05-19
| | | | Text from David G Johnston
* doc: improve 9.4 release notesBruce Momjian2014-05-18
| | | | Patch by Andres Freund
* Misc message style and doc fixes.Heikki Linnakangas2014-05-15
| | | | Euler Taveira
* doc: Clarify what files pg_basebackup omits from data directoryPeter Eisentraut2014-05-14
|
* pg_upgrade: error out on 'line' data type usageBruce Momjian2014-05-14
| | | | | The data type internal format changed in 9.4. Also mention this in the 9.4 release notes.
* doc: fix 9.4 release notes typoBruce Momjian2014-05-14
| | | | Report by Dean Rasheed
* doc: fix typo in 9.4 release note commentsBruce Momjian2014-05-14
| | | | Patch by Sergey Muraviov
* docs: mention windows quoting change in 9.4 release notesBruce Momjian2014-05-14
| | | | Report by Heikki Linnakangas
* doc: auto-updatable view adjustments for 9.4 release notesBruce Momjian2014-05-14
| | | | Report by Dean Rasheed
* docs: 9.4 release notes adjustmentsBruce Momjian2014-05-13
| | | | Patch by Andres Freund, slight adjustments by me
* docs: use structfield instead of structname in 9.4 release notesBruce Momjian2014-05-12
| | | | Where appropriate
* doc: 9.4 release note adjustmentsBruce Momjian2014-05-12
| | | | Report by Nicolas Barbier, Tatsuo Ishii, MauMau
* Fix typo in test_shm_mq document.Fujii Masao2014-05-13
| | | | Amit Langote
* Rename jsonb_hash_ops to jsonb_path_ops.Tom Lane2014-05-11
| | | | | | | | | | | | | There's no longer much pressure to switch the default GIN opclass for jsonb, but there was still some unhappiness with the name "jsonb_hash_ops", since hashing is no longer a distinguishing property of that opclass, and anyway it seems like a relatively minor detail. At the suggestion of Heikki Linnakangas, we'll use "jsonb_path_ops" instead; that captures the important characteristic that each index entry depends on the entire path from the document root to the indexed value. Also add a user-facing explanation of the implementation properties of these two opclasses.
* docs: Mark 9.4 release notes as current as of todayBruce Momjian2014-05-10
|
* Rename min_recovery_apply_delay to recovery_min_apply_delay.Tom Lane2014-05-10
| | | | | | | Per discussion, this seems like a more consistent choice of name. Fabrízio de Royes Mello, after a suggestion by Peter Eisentraut; some additional documentation wordsmithing by me
* More work on the JSON/JSONB user documentation.Tom Lane2014-05-10
| | | | | | Document existence operator adequately; fix obsolete claim that no Unicode-escape semantic checks happen on input (it's still true for json, but not for jsonb); improve examples; assorted wordsmithing.
* Fix bogus documentation of json_object_agg().Tom Lane2014-05-09
| | | | It takes two arguments, not one.
* Improve user-facing JSON documentation.Tom Lane2014-05-09
| | | | | | I started out with the intention of just fixing the info about the jsonb operator classes, but soon found myself copy-editing most of the JSON material. Hopefully it's more readable now.
* Document permissions needed for pg_database_size and pg_tablespace_size.Tom Lane2014-05-08
| | | | | | | Back in 8.3, we installed permissions checks in these functions (see commits 8bc225e7990a and cc26599b7206). But we forgot to document that anywhere in the user-facing docs; it did get mentioned in the 8.3 release notes, but nobody's looking at that any more. Per gripe from Suya Huang.
* Increase the default value of effective_cache_size to 4GB.Tom Lane2014-05-08
| | | | | | | | | | Per discussion, the old value of 128MB is ridiculously small on modern machines; in fact, it's not even any larger than the default value of shared_buffers, which it certainly should be. Increase to 4GB, which is unlikely to be any worse than the old default for anyone, and should be noticeably better for most. Eventually we might have an autotuning scheme for this setting, but the recent attempt crashed and burned, so for now just do this.
* Revert "Auto-tune effective_cache size to be 4x shared buffers"Tom Lane2014-05-08
| | | | | | | | | | | | | | This reverts commit ee1e5662d8d8330726eaef7d3110cb7add24d058, as well as a remarkably large number of followup commits, which were mostly concerned with the fact that the implementation didn't work terribly well. It still doesn't: we probably need some rather basic work in the GUC infrastructure if we want to fully support GUCs whose default varies depending on the value of another GUC. Meanwhile, it also emerged that there wasn't really consensus in favor of the definition the patch tried to implement (ie, effective_cache_size should default to 4 times shared_buffers). So whack it all back to where it was. In a followup commit, I'll do what was recently agreed to, which is to simply change the default to a higher value.
* When a background worker exists with code 0, unregister it.Robert Haas2014-05-07
| | | | | | | The previous behavior was to restart immediately, which was generally viewed as less useful. Petr Jelinek, with some adjustments by me.
* doc: Fix DocBook XML validityPeter Eisentraut2014-05-06
| | | | | | | | | | | | | | | | | | | | | | | | | The main problem is that DocBook SGML allows indexterm elements just about everywhere, but DocBook XML is stricter. For example, this common pattern <varlistentry> <indexterm>...</indexterm> <term>...</term> ... </varlistentry> needs to be changed to something like <varlistentry> <term>...<indexterm>...</indexterm></term> ... </varlistentry> See also bb4eefe7bf518e42c73797ea37b033a5d8a8e70a. There is currently nothing in the build system that enforces that things stay valid, because that requires additional tools and will receive separate consideration.
* More rewording of pg_stat_statements for 9.4 release notesBruce Momjian2014-05-06
| | | | Report by Amit Langote
* Update 9.4 release notes for queryid controlBruce Momjian2014-05-05
|
* Move pg_stat_statements into its on 9.4 release note sectionBruce Momjian2014-05-05
|
* In 9.4 release notes, add detail to pg_stat_statements itemsBruce Momjian2014-05-05
|
* Improve JSONB 9.4 release textBruce Momjian2014-05-05
|
* Add doc links to 9.4 release notes, and add major features listBruce Momjian2014-05-05
|
* Add SGML markup tags to 9.4 release notesBruce Momjian2014-05-05
|
* Update "huge pages" description in the 9.4 release notesBruce Momjian2014-05-05
|
* Update 9.4 release notes with feedback from the hackers listBruce Momjian2014-05-05
|
* doc: In FDW handler docs, mark up scan_clauses with <literal>.Robert Haas2014-05-05
| | | | Etsuro Fujita
* Add missing 9.4 release file.Bruce Momjian2014-05-04
|
* Initial version of Postgres 9.4 release notesBruce Momjian2014-05-03
|
* doc: Update pg_basebackup version compatibility claim for 9.4Peter Eisentraut2014-05-01
|
* Documentation corrections for pg_replication_slots.Robert Haas2014-04-30
| | | | Thomas Reiss, with changes to the catalog_xmin language by me.
* Rationalize common/relpath.[hc].Tom Lane2014-04-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit a73018392636ce832b09b5c31f6ad1f18a4643ea created rather a mess by putting dependencies on backend-only include files into include/common. We really shouldn't do that. To clean it up: * Move TABLESPACE_VERSION_DIRECTORY back to its longtime home in catalog/catalog.h. We won't consider this symbol part of the FE/BE API. * Push enum ForkNumber from relfilenode.h into relpath.h. We'll consider relpath.h as the source of truth for fork numbers, since relpath.c was already partially serving that function, and anyway relfilenode.h was kind of a random place for that enum. * So, relfilenode.h now includes relpath.h rather than vice-versa. This direction of dependency is fine. (That allows most, but not quite all, of the existing explicit #includes of relpath.h to go away again.) * Push forkname_to_number from catalog.c to relpath.c, just to centralize fork number stuff a bit better. * Push GetDatabasePath from catalog.c to relpath.c; it was rather odd that the previous commit didn't keep this together with relpath(). * To avoid needing relfilenode.h in common/, redefine the underlying function (now called GetRelationPath) as taking separate OID arguments, and make the APIs using RelFileNode or RelFileNodeBackend into macro wrappers. (The macros have a potential multiple-eval risk, but none of the existing call sites have an issue with that; one of them had such a risk already anyway.) * Fix failure to follow the directions when "init" fork type was added; specifically, the errhint in forkname_to_number wasn't updated, and neither was the SGML documentation for pg_relation_size(). * Fix tablespace-path-too-long check in CreateTableSpace() to account for fork-name component of maximum-length pathnames. This requires putting FORKNAMECHARS into a header file, but it was rather useless (and actually unreferenced) where it was. The last couple of items are potentially back-patchable bug fixes, if anyone is sufficiently excited about them; but personally I'm not. Per a gripe from Christoph Berg about how include/common wasn't self-contained.