aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
* Update release notes for libpq feature change.Tom Lane2012-08-02
|
* Replace libpq's "row processor" API with a "single row" mode.Tom Lane2012-08-02
| | | | | | | | | | | | | | | | | | | | | After taking awhile to digest the row-processor feature that was added to libpq in commit 92785dac2ee7026948962cd61c4cd84a2d052772, we've concluded it is over-complicated and too hard to use. Leave the core infrastructure changes in place (that is, there's still a row processor function inside libpq), but remove the exposed API pieces, and instead provide a "single row" mode switch that causes PQgetResult to return one row at a time in separate PGresult objects. This approach incurs more overhead than proper use of a row processor callback would, since construction of a PGresult per row adds extra cycles. However, it is far easier to use and harder to break. The single-row mode still affords applications the primary benefit that the row processor API was meant to provide, namely not having to accumulate large result sets in memory before processing them. Preliminary testing suggests that we can probably buy back most of the extra cycles by micro-optimizing construction of the extra results, but that task will be left for another day. Marko Kreen
* Add documentation cross-reference for JSON functions.Tom Lane2012-08-01
| | | | Thom Brown
* pg_basebackup: stylistic adjustmentsAlvaro Herrera2012-07-31
| | | | | | | | | | | | | | The most user-visible part of this is to change the long options --statusint and --noloop to --status-interval and --no-loop, respectively, per discussion. Also, consistently enclose file names in double quotes, per our conventions; and consistently use the term "transaction log file" to talk about WAL segments. (Someday we may need to go over this terminology and make it consistent across the whole source code.) Finally, reflow the code to better fit in 80 columns, and have pgindent fix it up some more.
* Now that the diskchecker.pl author has updated the download link on hisBruce Momjian2012-07-30
| | | | | | website, revert the separate link to the download git repository. Backpatch from 9.0 to current.
* Update doc mention of diskchecker.pl to add URL for script; retain URLBruce Momjian2012-07-26
| | | | | | for description. Patch to 9.0 and later, where script is mentioned.
* Document that the pg_upgrade user of rsync might want to skip someBruce Momjian2012-07-26
| | | | | | files, like postmaster.pid. Backpatch to 9.2.
* Document that pg_basebackup will create its output directoryPeter Eisentraut2012-07-25
|
* Change syntax of new CHECK NO INHERIT constraintsAlvaro Herrera2012-07-24
| | | | | | | | | | The initially implemented syntax, "CHECK NO INHERIT (expr)" was not deemed very good, so switch to "CHECK (expr) NO INHERIT" instead. This way it looks similar to SQL-standards compliant constraint attribute. Backport to 9.2 where the new syntax and feature was introduced. Per discussion.
* Show step titles in the pg_upgrade man pagePeter Eisentraut2012-07-17
| | | | | | The upstream XSLT stylesheets missed that case. found by Álvaro Herrera
* Add link to PEP 394 regarding python2 vs python3 namingPeter Eisentraut2012-07-14
|
* Document that Log-Shipping Standby Servers cannot be upgraded byBruce Momjian2012-07-10
| | | | | | pg_upgrade. Backpatch to 9.2.
* Run newly-configured perltidy script on Perl files.Bruce Momjian2012-07-04
| | | | Run on HEAD and 9.2.
* Remove reference to default wal_buffers being 8Magnus Hagander2012-07-04
| | | | | | This hasn't been true since 9.1, when the default was changed to -1. Remove the reference completely, keeping the discussion of the parameter and it's shared memory effects on the config page.
* Remove references to PostgreSQL bundled on SolarisMagnus Hagander2012-07-04
| | | | | Also remove special references to downloads off pgfoundry since they are not correct - downloads are done through the main website.
* Fix typoMagnus Hagander2012-07-04
| | | | gabrielle
* Remove references to pgfoundry as recommended hosting platformMagnus Hagander2012-07-04
| | | | | pgfoundry is deprectaed and no longer accepting new projects, so we really shouldn't be directing people there.
* Update release notes for pg_terminate_backend changes.Robert Haas2012-06-27
|
* Allow pg_terminate_backend() to be used on backends with matching role.Robert Haas2012-06-27
| | | | | | | | A similar change was made previously for pg_cancel_backend, so now it all matches again. Dan Farina, reviewed by Fujii Masao, Noah Misch, and Jeff Davis, with slight kibitzing on the doc changes by me.
* Make placeholders in SQL command help more consistent and precisePeter Eisentraut2012-06-22
| | | | | To avoid divergent names on related pages, avoid ambiguities, and reduce translation work a little.
* Remove confusing half sentence from legal noticePeter Eisentraut2012-06-20
| | | | pointed out by Stefan Kaltenbrunner
* Make documentation of --help and --version options more consistentPeter Eisentraut2012-06-18
| | | | | | Before, some places didn't document the short options (-? and -V), some documented both, some documented nothing, and they were listed in various orders. Now this is hopefully more consistent and complete.
* Reorder basebackup options, to list pg_basebackup firstMagnus Hagander2012-06-17
| | | | | | | Since this is the easy way of doing it, it should be listed first. All the old information is retained for those who want the more advanced way. Also adds a subheading for compressing logs, that seems to have been missing
* Remove release note entry for reverted patch.Tom Lane2012-06-13
|
* Fix description of SQL-standard meaning of CREATE LOCAL TEMP TABLE.Tom Lane2012-06-13
| | | | I had this slightly wrong, as noted by Noah Misch.
* Deprecate use of GLOBAL and LOCAL in temp table creation.Tom Lane2012-06-13
| | | | | | | | | | | | | Aside from adjusting the documentation to say that these are deprecated, we now report a warning (not an error) for use of GLOBAL, since it seems fairly likely that we might change that to request SQL-spec-compliant temp table behavior in the foreseeable future. Although our handling of LOCAL is equally nonstandard, there is no evident interest in ever implementing SQL modules, and furthermore some other products interpret LOCAL as behaving the same way we do. So no expectation of change and no warning for LOCAL; but it still seems a good idea to deprecate writing it. Noah Misch
* Support Linux's oom_score_adj API as well as the older oom_adj API.Tom Lane2012-06-13
| | | | | | | | | The simplest way to handle this is just to copy-and-paste the relevant code block in fork_process.c, so that's what I did. (It's possible that something more complicated would be useful to packagers who want to work with either the old or the new API; but at this point the number of such people is rapidly approaching zero, so let's just get the minimal thing done.) Update relevant documentation as well.
* Improve documentation of postgres -C optionPeter Eisentraut2012-06-13
| | | | | | Clarify help (s/return/print/), and explain that this option is for use by other programs, not for user-facing use (it does not print units).
* Copy-editing of release notes.Robert Haas2012-06-12
| | | | | | | Remove a couple of items that were actually back-patched bug fixes. Add additional details to a couple of items which lacked a description. Improve attributions for a couple of items I was involved with. A few other miscellaneous corrections.
* pg_receivexlog: Rename option --dir to --directoryPeter Eisentraut2012-06-12
| | | | | | | | getopt_long() allows abbreviating long options, so we might as well give the option the full name, and users can abbreviate it how they like. Do some general polishing of the --help output at the same time.
* Revert behaviour of -x/--xlog to 9.1 semanticsMagnus Hagander2012-06-11
| | | | | | | | To replace it, add -X/--xlog-method that allows the specification of fetch or stream. Do this to avoid unnecessary backwards-incompatiblity. Spotted and suggested by Peter Eisentraut.
* Fix pg_basebackup/pg_receivexlog for floating point timestampsMagnus Hagander2012-06-10
| | | | | | | Since the replication protocol deals with TimestampTz, we need to care for the floating point case as well in the frontend tools. Fujii Masao, with changes from Magnus Hagander
* Documentation style improvementsPeter Eisentraut2012-06-08
|
* Documentation spell and markup checkingPeter Eisentraut2012-06-08
|
* Fix typoMagnus Hagander2012-06-05
| | | | Noted by Erik Rijkers
* Add example of archive_command to use with pg_receivexlogMagnus Hagander2012-06-05
|
* Improve description of pg_stat_statements normalisation in release notes.Simon Riggs2012-06-01
|
* Clarify description of covering indexes in release notesSimon Riggs2012-06-01
|
* Copy editing of release notes for couple of my items.Simon Riggs2012-06-01
|
* Update release notes for 9.1.4, 9.0.8, 8.4.12, 8.3.19.Tom Lane2012-05-31
|
* Rewrite --section option to decouple it from --schema-only/--data-only.Tom Lane2012-05-29
| | | | | | | | | | | | | | | | | | | | | | | | | The initial implementation of pg_dump's --section option supposed that the existing --schema-only and --data-only options could be made equivalent to --section settings. This is wrong, though, due to dubious but long since set-in-stone decisions about where to dump SEQUENCE SET items, as seen in bug report from Martin Pitt. (And I'm not totally convinced there weren't other bugs, either.) Undo that coupling and instead drive --section filtering off current-section state tracked as we scan through the TOC list to call _tocEntryRequired(). To make sure those decisions don't shift around and hopefully save a few cycles, run _tocEntryRequired() only once per TOC entry and save the result in a new TOC field. This required minor rejiggering of ACL handling but also allows a far cleaner implementation of inhibit_data_for_failed_table. Also, to ensure that pg_dump and pg_restore have the same behavior with respect to the --section switches, add _tocEntryRequired() filtering to WriteToc() and WriteDataChunks(), rather than trying to implement section filtering in an entirely orthogonal way in dumpDumpableObject(). This required adjusting the handling of the special ENCODING and STDSTRINGS items, but they were pretty weird before anyway. Minor other code review for the patch, too.
* libpq: URI parsing fixesPeter Eisentraut2012-05-28
| | | | | | | | | | | | | | | Drop special handling of host component with slashes to mean Unix-domain socket. Specify it as separate parameter or using percent-encoding now. Allow omitting username, password, and port even if the corresponding designators are present in URI. Handle percent-encoding in query parameter keywords. Alex Shulgin some documentation improvements by myself
* Make pg_recievexlog by default loop on connection failuresMagnus Hagander2012-05-27
| | | | | | Avoids the need for an external script in the most common scenario. Behavior can be overridden using the -n/--noloop commandline parameter.
* Clarify 9.2 release notes items about pg_stat_statements, to betterBruce Momjian2012-05-24
| | | | | document fix of double counting and read/write count addition, per Peter Geoghegan
* Change pg_stat_statements order of release note items, per PeterBruce Momjian2012-05-24
| | | | Geoghegan
* Remove PL/Perl null array 9.2 release note item, per Andrew DunstanBruce Momjian2012-05-24
|
* Update SQL key word list to SQL:2011Peter Eisentraut2012-05-24
| | | | | For space reasons, drop SQL:1999 and SQL:2003. Only keep the latest two and SQL-92 for historical comparison.
* Mention Peter Geoghegan as primary author of pg_stat_statements changes.Bruce Momjian2012-05-23
|
* Improve wording of 9.2 clog release note item.Bruce Momjian2012-05-23
|
* Add 9.2 release note authorship mentions for Heikki and AlexanderBruce Momjian2012-05-22
| | | | Korotkov, per Alexander Korotkov.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-27 06:08:05 +0000