- 07 Jun, 2010 1 commit
-
-
Itagaki Takahiro authored
Almost all of the terms in docs and messages were replaced, but still remains in a few comments and README files in codes.
-
- 03 May, 2010 1 commit
-
-
Heikki Linnakangas authored
the PITR documentation to mention that you need to set wal_level to 'archive' or 'hot_standby', to enable WAL archiving. Per Simon's request.
-
- 29 Apr, 2010 1 commit
-
-
Tom Lane authored
to perform a backup without archive_mode being enabled. This gives up some user-error protection in order to improve usefulness for streaming-replication scenarios. Per discussion.
-
- 28 Apr, 2010 1 commit
-
-
Heikki Linnakangas authored
archival or hot standby should be WAL-logged, instead of deducing that from other options like archive_mode. This replaces recovery_connections GUC in the primary, where it now has no effect, but it's still used in the standby to enable/disable hot standby. Remove the WAL-logging of "unlogged operations", like creating an index without WAL-logging and fsyncing it at the end. Instead, we keep a copy of the wal_mode setting and the settings that affect how much shared memory a hot standby server needs to track master transactions (max_connections, max_prepared_xacts, max_locks_per_xact) in pg_control. Whenever the settings change, at server restart, write a WAL record noting the new settings and update pg_control. This allows us to notice the change in those settings in the standby at the right moment, they used to be included in checkpoint records, but that meant that a changed value was not reflected in the standby until the first checkpoint after the change. Bump PG_CONTROL_VERSION and XLOG_PAGE_MAGIC. Whack XLOG_PAGE_MAGIC back to the sequence it used to follow, before hot standby and subsequent patches changed it to 0x9003.
-
- 20 Apr, 2010 1 commit
-
-
Robert Haas authored
In 8.4 and prior, WAL-logging could potentially be skipped whenever archive_mode=off. With streaming replication, this is now true only if max_wal_senders=0. Fujii Masao, with light copyediting by me
-
- 12 Apr, 2010 1 commit
-
-
Bruce Momjian authored
archiving example, per suggestion from Greg Smith.
-
- 03 Apr, 2010 1 commit
-
-
Peter Eisentraut authored
The endterm attribute is mainly useful when the toolchain does not support automatic link target text generation for a particular situation. In the past, this was required by the man page tools for all reference page links, but that is no longer the case, and it now actually gets in the way of proper automatic link text generation. The only remaining use cases are currently xrefs to refsects.
-
- 01 Apr, 2010 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 31 Mar, 2010 3 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 22 Feb, 2010 2 commits
-
-
Bruce Momjian authored
used for continuous archiving.
-
Heikki Linnakangas authored
They used to be scattered between the "backup and restore" and "streaming replication" chapters.
-
- 19 Feb, 2010 1 commit
-
-
Bruce Momjian authored
Greg Smith
-
- 09 Feb, 2010 1 commit
-
-
Heikki Linnakangas authored
sections under "High Availability, Load Balancing, and Replication" chapter. Streaming replication chapter needs a lot more work, but this commit just moves things around.
-
- 03 Feb, 2010 1 commit
-
-
Bruce Momjian authored
-
- 26 Jan, 2010 1 commit
-
-
Peter Eisentraut authored
to make it easier to use with tabs.
-
- 24 Jan, 2010 1 commit
-
-
Magnus Hagander authored
-
- 23 Jan, 2010 1 commit
-
-
Simon Riggs authored
woken by alarm we send SIGUSR1 to all backends requesting that they check to see if they are blocking Startup process. If so, they throw ERROR/FATAL as for other conflict resolutions. Deadlock stop gap removed. max_standby_delay = -1 option removed to prevent deadlock.
-
- 15 Jan, 2010 1 commit
-
-
Heikki Linnakangas authored
This includes two new kinds of postmaster processes, walsenders and walreceiver. Walreceiver is responsible for connecting to the primary server and streaming WAL to disk, while walsender runs in the primary server and streams WAL from disk to the client. Documentation still needs work, but the basics are there. We will probably pull the replication section to a new chapter later on, as well as the sections describing file-based replication. But let's do that as a separate patch, so that it's easier to see what has been added/changed. This patch also adds a new section to the chapter about FE/BE protocol, documenting the protocol used by walsender/walreceivxer. Bump catalog version because of two new functions, pg_last_xlog_receive_location() and pg_last_xlog_replay_location(), for monitoring the progress of replication. Fujii Masao, with additional hacking by me
-
- 12 Jan, 2010 1 commit
-
-
Bruce Momjian authored
-
- 10 Jan, 2010 1 commit
-
-
Simon Riggs authored
Adding missing docs for previous Hot Standby patch.
-
- 20 Dec, 2009 1 commit
-
-
Robert Haas authored
John Naylor
-
- 19 Dec, 2009 2 commits
-
-
Bruce Momjian authored
-
Simon Riggs authored
Enabled by recovery_connections = on (default) and forcing archive recovery using a recovery.conf. Recovery processing now emulates the original transactions as they are replayed, providing full locking and MVCC behaviour for read only queries. Recovery must enter consistent state before connections are allowed, so there is a delay, typically short, before connections succeed. Replay of recovering transactions can conflict and in some cases deadlock with queries during recovery; these result in query cancellation after max_standby_delay seconds have expired. Infrastructure changes have minor effects on normal running, though introduce four new types of WAL record. New test mode "make standbycheck" allows regression tests of static command behaviour on a standby server while in recovery. Typical and extreme dynamic behaviours have been checked via code inspection and manual testing. Few port specific behaviours have been utilised, though primary testing has been on Linux only so far. This commit is the basic patch. Additional changes will follow in this release to enhance some aspects of behaviour, notably improved handling of conflicts, deadlock detection and query cancellation. Changes to VACUUM FULL are also required. Simon Riggs, with significant and lengthy review by Heikki Linnakangas, including streamlined redesign of snapshot creation and two-phase commit. Important contributions from Florian Pflug, Mark Kirkwood, Merlin Moncure, Greg Stark, Gianni Ciolli, Gabriele Bartolini, Hannu Krosing, Robert Haas, Tatsuo Ishii, Hiroyuki Yamada plus support and feedback from many other community members.
-
- 07 Aug, 2009 1 commit
-
-
Alvaro Herrera authored
-
- 26 Jun, 2009 1 commit
-
-
Tom Lane authored
-
- 05 Jun, 2009 1 commit
-
-
Bruce Momjian authored
Fujii Masao
-
- 27 May, 2009 1 commit
-
-
Bruce Momjian authored
-
- 14 May, 2009 1 commit
-
-
Heikki Linnakangas authored
is run at the end of archive recovery, providing a chance to do external cleanup. Modify pg_standby so that it no longer removes the trigger file, that is to be done using the recovery_end_command now. Provide a "smart" failover mode in pg_standby, where we don't fail over immediately, but only after recovering all unapplied WAL from the archive. That gives you zero data loss assuming all WAL was archived before failover, which is what most users of pg_standby actually want. recovery_end_command by Simon Riggs, pg_standby changes by Fujii Masao and myself.
-
- 27 Apr, 2009 1 commit
-
-
Bruce Momjian authored
and SQL).
-
- 07 Apr, 2009 1 commit
-
-
Tom Lane authored
the checkpoint in immediate or lazy mode. This is to address complaints that pg_start_backup() takes a long time even when there's no need to minimize its I/O consumption.
-
- 05 Mar, 2009 1 commit
-
-
Tom Lane authored
in favor of log_checkpoints. Fujii Masao
-
- 13 Jan, 2009 1 commit
-
-
Bruce Momjian authored
-
- 09 Nov, 2008 1 commit
-
-
Tom Lane authored
If the latter doesn't exist, automatically recreate it. (We don't do this for pg_xlog, though, per discussion.) Jonah Harris
-
- 18 Jul, 2008 1 commit
-
-
Bruce Momjian authored
ITAGAKI Takahiro
-
- 23 Jun, 2008 1 commit
-
-
Bruce Momjian authored
Joshua D. Drake
-
- 09 Apr, 2008 1 commit
-
-
Bruce Momjian authored
you can't get a simultaneous snapshot.
-
- 05 Apr, 2008 1 commit
-
-
Bruce Momjian authored
returing right away. This guarantees that when pg_stop_backup() returns, you have a valid backup. Simon Riggs
-