1. 07 Jun, 2010 1 commit
  2. 03 May, 2010 1 commit
  3. 29 Apr, 2010 1 commit
  4. 28 Apr, 2010 1 commit
    • Heikki Linnakangas's avatar
      Introduce wal_level GUC to explicitly control if information needed for · 9b8a7332
      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.
      9b8a7332
  5. 20 Apr, 2010 1 commit
    • Robert Haas's avatar
      Update docs as to when WAL logging can be skipped. · ee7769bb
      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
      ee7769bb
  6. 12 Apr, 2010 1 commit
  7. 03 Apr, 2010 1 commit
    • Peter Eisentraut's avatar
      Remove unnecessary xref endterm attributes and title ids · 6dcce398
      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.
      6dcce398
  8. 01 Apr, 2010 2 commits
  9. 31 Mar, 2010 3 commits
  10. 22 Feb, 2010 2 commits
  11. 19 Feb, 2010 1 commit
  12. 09 Feb, 2010 1 commit
  13. 03 Feb, 2010 1 commit
  14. 26 Jan, 2010 1 commit
  15. 24 Jan, 2010 1 commit
  16. 23 Jan, 2010 1 commit
    • Simon Riggs's avatar
      In HS, Startup process sets SIGALRM when waiting for buffer pin. If · 959ac58c
      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.
      959ac58c
  17. 15 Jan, 2010 1 commit
    • Heikki Linnakangas's avatar
      Introduce Streaming Replication. · 40f908bd
      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
      40f908bd
  18. 12 Jan, 2010 1 commit
  19. 10 Jan, 2010 1 commit
  20. 20 Dec, 2009 1 commit
  21. 19 Dec, 2009 2 commits
    • Bruce Momjian's avatar
      Convert tabs to spaces in SGML. · 7ba1f8fc
      Bruce Momjian authored
      7ba1f8fc
    • Simon Riggs's avatar
      Allow read only connections during recovery, known as Hot Standby. · efc16ea5
      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.
      efc16ea5
  22. 07 Aug, 2009 1 commit
  23. 26 Jun, 2009 1 commit
  24. 05 Jun, 2009 1 commit
  25. 27 May, 2009 1 commit
  26. 14 May, 2009 1 commit
    • Heikki Linnakangas's avatar
      Add recovery_end_command option to recovery.conf. recovery_end_command · 9e403c25
      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.
      9e403c25
  27. 27 Apr, 2009 1 commit
  28. 07 Apr, 2009 1 commit
  29. 05 Mar, 2009 1 commit
  30. 13 Jan, 2009 1 commit
  31. 09 Nov, 2008 1 commit
  32. 18 Jul, 2008 1 commit
  33. 23 Jun, 2008 1 commit
  34. 09 Apr, 2008 1 commit
  35. 05 Apr, 2008 1 commit