replication_slots usability issue

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: replication_slots usability issue
Date: 2018-10-29 17:31:56
Message-ID: 56672097-711c-126a-a63e-04e7940110ad@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-Hackers,

Working on 9.6 today (unsure if fixed in newer versions). Had an issue
where the wal was 280G despite max_wal_size being 8G. Found out there
were stale replication slots from a recent base backup. I went to drop
the replication slots and found that since the wal_level was set to
minimal vs replica or higher, I couldn't drop the replication slot.
Clearly that makes sense for creating a replication slot but it seems
like an artificial limitation for dropping them.

JD

--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
*** A fault and talent of mine is to tell it exactly how it is. ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
***** Unless otherwise stated, opinions are my own. *****

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-10-29 18:26:56 Re: replication_slots usability issue
Previous Message Paul A Jungwirth 2018-10-29 17:29:37 Re: date_trunc() in a specific time zone