- 05 7月, 2013 1 次提交
-
-
由 Magnus Hagander 提交于
Reported by Kevin Hale Boyes
-
- 04 7月, 2013 1 次提交
-
-
由 Robert Haas 提交于
In 9.3, there's no particular limit on the number of bgworkers; instead, we just count up the number that are actually registered, and use that to set MaxBackends. However, that approach causes problems for Hot Standby, which needs both MaxBackends and the size of the lock table to be the same on the standby as on the master, yet it may not be desirable to run the same bgworkers in both places. 9.3 handles that by failing to notice the problem, which will probably work fine in nearly all cases anyway, but is not theoretically sound. A further problem with simply counting the number of registered workers is that new workers can't be registered without a postmaster restart. This is inconvenient for administrators, since bouncing the postmaster causes an interruption of service. Moreover, there are a number of applications for background processes where, by necessity, the background process must be started on the fly (e.g. parallel query). While this patch doesn't actually make it possible to register new background workers after startup time, it's a necessary prerequisite. Patch by me. Review by Michael Paquier.
-
- 03 7月, 2013 1 次提交
-
-
由 Alvaro Herrera 提交于
Make it easier for readers of the FP docs to find out about possibly truncated values. Per complaint from Tom Duffey in message F0E0F874-C86F-48D1-AA2A-0C5365BF5118@trillitech.com Author: Albe Laurenz Reviewed by: Abhijit Menon-Sen
-
- 20 6月, 2013 1 次提交
-
-
由 Fujii Masao 提交于
Patch by Simon Riggs, reviewed by Jeff Janes and me.
-
- 21 5月, 2013 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 06 5月, 2013 1 次提交
-
-
由 Bruce Momjian 提交于
Removal of doc adjustment and release note mention as well.
-
- 05 5月, 2013 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Restore 4-byte designation for docs. Fix 9.3 doc query to properly pad to four digits. Backpatch to all active branches Per suggestions from Ian Lawrence Barwick
-
- 04 5月, 2013 1 次提交
-
-
由 Bruce Momjian 提交于
Backpatch to 9.2. Report from Ian Lawrence Barwick
-
- 28 3月, 2013 2 次提交
-
-
由 Simon Riggs 提交于
-
由 Kevin Grittner 提交于
Commit bc5334d8 accidentally included a second <variablelist> tag for a new list item.
-
- 27 3月, 2013 1 次提交
-
-
由 Simon Riggs 提交于
If required, recovery.conf can now be located outside of the data directory. Server needs read/write permissions on this directory.
-
- 24 3月, 2013 1 次提交
-
-
由 Tom Lane 提交于
Doing that results in a broken index entry in PDF output. We had only a few like that, which is probably why nobody noticed before. Standardize on putting the <term> first. Josh Kupershmidt
-
- 22 3月, 2013 2 次提交
-
-
由 Simon Riggs 提交于
Checksums are set immediately prior to flush out of shared buffers and checked when pages are read in again. Hint bit setting will require full page write when block is dirtied, which causes various infrastructure changes. Extensive comments, docs and README. WARNING message thrown if checksum fails on non-all zeroes page; ERROR thrown but can be disabled with ignore_checksum_failure = on. Feature enabled by an initdb option, since transition from option off to option on is long and complex and has not yet been implemented. Default is not to use checksums. Checksum used is WAL CRC-32 truncated to 16-bits. Simon Riggs, Jeff Davis, Greg Smith Wide input and assistance from many community members. Thank you.
- 17 3月, 2013 1 次提交
-
-
由 Tom Lane 提交于
This GUC allows limiting the time spent waiting to acquire any one heavyweight lock. In support of this, improve the recently-added timeout infrastructure to permit efficiently enabling or disabling multiple timeouts at once. That reduces the performance hit from turning on lock_timeout, though it's still not zero. Zoltán Böszörményi, reviewed by Tom Lane, Stephen Frost, and Hari Babu
-
- 16 3月, 2013 1 次提交
-
-
由 Tom Lane 提交于
Clarify the docs explaining what commit_delay does, and add a recommendation about a useful value for it, namely half of the single-page fsync time reported by pg_test_fsync. This is informed by testing of the new-in-9.3 implementation of commit_delay; in prior versions it was far harder to arrive at a useful setting. In passing, do some wordsmithing and markup-fixing in the same general area. Also, change pg_test_fsync's default time-per-test from 2 seconds to 5. The old value was about the minimum at which the results could be taken seriously at all, and so seems a tad optimistic as a default. Peter Geoghegan, reviewed by Noah Misch; some additional editing by me
-
- 11 3月, 2013 1 次提交
-
-
由 Peter Eisentraut 提交于
suggested by Tianyin Xu
-
- 05 2月, 2013 1 次提交
-
-
由 Simon Riggs 提交于
Revert commit 84725aa5
-
- 03 2月, 2013 1 次提交
-
-
由 Simon Riggs 提交于
Following bug analysis of #7819 by Tom Lane
-
- 26 1月, 2013 3 次提交
-
-
由 Bruce Momjian 提交于
0e93959a Revert patch that modified doc index mentions of search_path Per Peter E.
-
由 Bruce Momjian 提交于
per Tianyin Xu
-
由 Bruce Momjian 提交于
Karl O. Pinc
-
- 04 12月, 2012 4 次提交
-
-
由 Bruce Momjian 提交于
storage. Have pg_upgrade use it, and enable server options fsync=off and full_page_writes=off. Document that users turning fsync from off to on should run initdb --sync-only. [ Previous commit was incorrectly applied as a git merge. ]
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 18 11月, 2012 1 次提交
-
-
由 Peter Eisentraut 提交于
Karl O. Pinc
-
- 01 11月, 2012 1 次提交
-
-
由 Tom Lane 提交于
Per bug #7631 from Rob Johnson. The code is operating as designed, but the docs didn't explain it.
-
- 11 10月, 2012 1 次提交
-
-
由 Heikki Linnakangas 提交于
Rename replication_timeout to wal_sender_timeout, and add a new setting called wal_receiver_timeout that does the same at the walreceiver side. There was previously no timeout in walreceiver, so if the network went down, for example, the walreceiver could take a long time to notice that the connection was lost. Now with the two settings, both sides of a replication connection will detect a broken connection similarly. It is no longer necessary to manually set wal_receiver_status_interval to a value smaller than the timeout. Both wal sender and receiver now automatically send a "ping" message if more than 1/2 of the configured timeout has elapsed, and it hasn't received any messages from the other end. Amit Kapila, heavily edited by me.
-
- 08 10月, 2012 1 次提交
-
-
由 Tom Lane 提交于
Copy-editing for previous patch, plus fixing some longstanding markup issues and oversights (like not mentioning that failures will set the PQerrorMessage string).
-
- 01 10月, 2012 1 次提交
-
-
由 Heikki Linnakangas 提交于
Jeff Janes
-
- 24 9月, 2012 1 次提交
-
-
由 Heikki Linnakangas 提交于
This allows easily splitting configuration into many files, deployed in a directory. Magnus Hagander, Greg Smith, Selena Deckelmann, reviewed by Noah Misch.
-
- 18 9月, 2012 1 次提交
-
-
由 Tom Lane 提交于
Somewhere along the line, somebody decided to remove all trace of this notation from the documentation text. It was still in the command syntax synopses, or at least some of them, but with no indication what it meant. This will not do, as evidenced by the confusion apparent in bug #7543; even if the notation is now unnecessary, people will find it in legacy SQL code and need to know what it does.
-
- 31 8月, 2012 1 次提交
-
-
由 Bruce Momjian 提交于
queries on parent tables, per suggestion from Josh Berkus.
-
- 23 8月, 2012 3 次提交
-
-
由 Tom Lane 提交于
The docs claimed that this mode only waits for the standby to receive WAL data, but actually it waits for the data to be written out to the standby's OS; which is a pretty significant difference because it removes the risk of crash of the walreceiver process.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
configuration file.
-
- 11 8月, 2012 1 次提交
-
-
由 Tom Lane 提交于
Replace unix_socket_directory with unix_socket_directories, which is a list of socket directories, and adjust postmaster's code to allow zero or more Unix-domain sockets to be created. This is mostly a straightforward change, but since the Unix sockets ought to be created after the TCP/IP sockets for safety reasons (better chance of detecting a port number conflict), AddToDataDirLockFile needs to be fixed to support out-of-order updates of data directory lockfile lines. That's a change that had been foreseen to be necessary someday anyway. Honza Horak, reviewed and revised by Tom Lane
-
- 10 8月, 2012 1 次提交
-
-
由 Magnus Hagander 提交于
Should be limited to the maximum number of connections excluding autovacuum workers, not including. Add similar check for max_wal_senders, which should never be higher than max_connections.
-