aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2014-11-18 02:32:48 +0900
committerFujii Masao <fujii@postgresql.org>2014-11-18 02:32:48 +0900
commitc4f99d20294950576d552dcaf9ce5b9bdc4233a3 (patch)
tree86cf847e5b9ea660d9909146bff031568b137f51 /src/backend/access/gist/gist.c
parentbc241488b0f9bde3e14094bfaf0d7987fafb6600 (diff)
downloadpostgresql-c4f99d20294950576d552dcaf9ce5b9bdc4233a3.tar.gz
postgresql-c4f99d20294950576d552dcaf9ce5b9bdc4233a3.zip
Add --synchronous option to pg_receivexlog, for more reliable WAL writing.
Previously pg_receivexlog flushed WAL data only when WAL file was switched. Then 3dad73e added -F option to pg_receivexlog so that users could control how frequently sync commands were issued to WAL files. It also allowed users to make pg_receivexlog flush WAL data immediately after writing by specifying 0 in -F option. However feedback messages were not sent back immediately even after a flush location was updated. So even if WAL data was flushed in real time, the server could not see that for a while. This commit removes -F option from and adds --synchronous to pg_receivexlog. If --synchronous is specified, like the standby's wal receiver, pg_receivexlog flushes WAL data as soon as there is WAL data which has not been flushed yet. Then it sends back the feedback message identifying the latest flush location to the server. This option is useful to make pg_receivexlog behave as sync standby by using replication slot, for example. Original patch by Furuya Osamu, heavily rewritten by me. Reviewed by Heikki Linnakangas, Alvaro Herrera and Sawada Masahiko.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions