- 21 6月, 2011 1 次提交
-
-
由 Tom Lane 提交于
Also be more careful about markup: use & not just &.
-
- 18 6月, 2011 1 次提交
-
-
由 Tom Lane 提交于
This is a dangerous example to provide because on machines with GNU cp, it will silently do the wrong thing and risk archive corruption. Worse, during the 9.0 cycle somebody "improved" the discussion by removing the warning that used to be there about that, and instead leaving the impression that the command would work as desired on most Unixen. It doesn't. Try to rectify the damage by providing an example that is safe most everywhere, and then noting that you can try cp -i if you want but you'd better test that. In back-patching this to all supported branches, I also added an example command for Windows, which wasn't provided before 9.0.
-
- 19 5月, 2011 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 08 5月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 09 2月, 2011 1 次提交
-
-
由 Simon Riggs 提交于
new recovery.conf parameter recovery_target_name allows PITR to specify named points as recovery targets. Jaime Casanova, reviewed by Euler Taveira de Oliveira, plus minor edits
-
- 07 2月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 02 2月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 01 2月, 2011 2 次提交
-
-
由 Bruce Momjian 提交于
Operation", merged from upgrade sections in "Installation from Source Code" and "Backup and Restore". This now gives a single place for all upgrade information.
-
由 Heikki Linnakangas 提交于
With this patch, pg_basebackup doesn't write a backup_label file in the data directory, so it doesn't interfere with a pg_start/stop_backup() based backup anymore. backup_label is still included in the backup, but it is injected directly into the tar stream. Heikki Linnakangas, reviewed by Fujii Masao and Magnus Hagander.
-
- 30 1月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
capitalization.
-
- 23 1月, 2011 1 次提交
-
-
由 Magnus Hagander 提交于
This tool makes it possible to do the pg_start_backup/ copy files/pg_stop_backup step in a single command. There are still some steps to be done before this is a complete backup solution, such as the ability to stream the required WAL logs, but it's still usable, and could do with some buildfarm coverage. In passing, make the checkpoint request optionally fast instead of hardcoding it. Magnus Hagander, reviewed by Fujii Masao and Dimitri Fontaine
-
- 25 11月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
reduce recovery time.
-
- 21 9月, 2010 1 次提交
-
-
由 Magnus Hagander 提交于
-
- 13 9月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
it doesn't work. Backpatch to 9.0.X.
-
- 12 9月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
Backpatch to 9.0.X.
-
- 16 8月, 2010 1 次提交
-
-
由 Tom Lane 提交于
-
- 07 6月, 2010 1 次提交
-
-
由 Itagaki Takahiro 提交于
Almost all of the terms in docs and messages were replaced, but still remains in a few comments and README files in codes.
-
- 03 5月, 2010 1 次提交
-
-
由 Heikki Linnakangas 提交于
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.
-
- 30 4月, 2010 1 次提交
-
-
由 Tom Lane 提交于
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.
-
- 29 4月, 2010 1 次提交
-
-
由 Heikki Linnakangas 提交于
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 4月, 2010 1 次提交
-
-
由 Robert Haas 提交于
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
-
- 13 4月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
archiving example, per suggestion from Greg Smith.
-
- 03 4月, 2010 1 次提交
-
-
由 Peter Eisentraut 提交于
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 4月, 2010 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 23 2月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
used for continuous archiving.
-
- 22 2月, 2010 1 次提交
-
-
由 Heikki Linnakangas 提交于
They used to be scattered between the "backup and restore" and "streaming replication" chapters.
-
- 19 2月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
Greg Smith
-
- 10 2月, 2010 1 次提交
-
-
由 Heikki Linnakangas 提交于
sections under "High Availability, Load Balancing, and Replication" chapter. Streaming replication chapter needs a lot more work, but this commit just moves things around.
-
- 04 2月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 26 1月, 2010 1 次提交
-
-
由 Peter Eisentraut 提交于
to make it easier to use with tabs.
-
- 24 1月, 2010 2 次提交
-
-
由 Magnus Hagander 提交于
-
由 Simon Riggs 提交于
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 1月, 2010 1 次提交
-
-
由 Heikki Linnakangas 提交于
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 1月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 11 1月, 2010 1 次提交
-
-
由 Simon Riggs 提交于
Adding missing docs for previous Hot Standby patch.
-
- 20 12月, 2009 1 次提交
-
-
由 Robert Haas 提交于
John Naylor
-