aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2020-12-02 11:00:15 +0900
committerFujii Masao <fujii@postgresql.org>2020-12-02 11:00:15 +0900
commit942305a36365433eff3c1937945758f2dbf1662b (patch)
tree7023fb4da694ee4ff435baa8782e0b8e70530fa0 /src/backend/access/gist/gistxlog.c
parent87ae9691d25379785f8c0f81b06a14818cfd8c56 (diff)
downloadpostgresql-942305a36365433eff3c1937945758f2dbf1662b.tar.gz
postgresql-942305a36365433eff3c1937945758f2dbf1662b.zip
Allow restore_command parameter to be changed with reload.
This commit changes restore_command from PGC_POSTMASTER to PGC_SIGHUP. As the side effect of this commit, restore_command can be reset to empty during archive recovery. In this setting, archive recovery tries to replay only WAL files available in pg_wal directory. This is the same behavior as when the command that always fails is specified in restore_command. Note that restore_command still must be specified (not empty) when starting archive recovery, even after applying this commit. This is necessary as the safeguard to prevent users from forgetting to specify restore_command and starting archive recovery. Thanks to Peter Eisentraut, Michael Paquier, Andres Freund, Robert Haas and Anastasia Lubennikova for discussion. Author: Sergei Kornilov Reviewed-by: Kyotaro Horiguchi, Fujii Masao Discussion: https://postgr.es/m/2317771549527294@sas2-985f744271ca.qloud-c.yandex.net
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions