diff options
author | Robert Haas <rhaas@postgresql.org> | 2011-03-10 15:38:39 -0500 |
---|---|---|
committer | Robert Haas <rhaas@postgresql.org> | 2011-03-10 15:43:37 -0500 |
commit | b8bb8dbf20e13087f8e57ff4c42e81776ae5e545 (patch) | |
tree | d36a6d8bedd1eeece5ee980f116c12698bd37648 /src/backend/parser/parse_expr.c | |
parent | e397d2ee6474865becb8f99ac28586736788f1f2 (diff) | |
download | postgresql-b8bb8dbf20e13087f8e57ff4c42e81776ae5e545.tar.gz postgresql-b8bb8dbf20e13087f8e57ff4c42e81776ae5e545.zip |
More synchronous replication tweaks.
SyncRepRequested() must check not only the value of the
synchronous_replication GUC but also whether max_wal_senders > 0.
Otherwise, we might end up waiting for sync rep even when there's no
possibility of a standby ever managing to connect. There are some
existing cross-checks to prevent this, but they're not quite sufficient:
the user can start the server with max_wal_senders=0,
synchronous_standby_names='', and synchronous_replication=off and then
subsequent make synchronous_standby_names not empty using pg_ctl reload,
and then SET synchronous_standby=on, leading to an indefinite hang.
Along the way, rename the global variable for the synchronous_replication
GUC to match the name of the GUC itself, for clarity.
Report by Fujii Masao, though I didn't use his patch.
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions