aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2010-04-12 09:52:29 +0000
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2010-04-12 09:52:29 +0000
commite57cd7f0a1622138d5489477e0625741e036e940 (patch)
tree78e648e83c221f635bdf01cb424c3964a3680fbe /src/backend/access/gist/gistget.c
parent93f35f0955f4a9c7bda191f80e3b64ba509ce923 (diff)
downloadpostgresql-e57cd7f0a1622138d5489477e0625741e036e940.tar.gz
postgresql-e57cd7f0a1622138d5489477e0625741e036e940.zip
Change the logic to decide when to delete old WAL segments, so that it
doesn't take into account how far the WAL senders are. This way a hung WAL sender doesn't prevent old WAL segments from being recycled/removed in the primary, ultimately causing the disk to fill up. Instead add standby_keep_segments setting to control how many old WAL segments are kept in the primary. This also makes it more reliable to use streaming replication without WAL archiving, assuming that you set standby_keep_segments high enough.
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions