Re: [PATCH] Fix drop replication slot blocking instead of returning error
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Simone Gotti <simone.gotti@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2017-08-29T10:13:02Z
Lists: pgsql-hackers
Attachments
Simone Gotti wrote: > Hi all, > > I noticed that in postgres 10beta3, calling pg_drop_replication_slot on an > active slot will block until it's released instead of returning an error > like > done in pg 9.6. Since this is a change in the previous behavior and the docs > wasn't changed I made a patch to restore the previous behavior. Changing that behavior was the entire point of the cited commit. A better fix, from my perspective, is to amend the docs as per the attached patch. This is what would be useful for logical replication, which is what replication slots were invented for in the first place. If you disagree, let's discuss what other use cases you have, and we can come up with alternatives that satisfy both. I think a decent answer, but one which would create a bit of extra churn, would be to have an optional boolean flag in the command/function for "nowait", instead of hardcoding either behavior. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Restore behavior for replication origin drop
- f15b76a9010d 10.0 landed
- a6979c3a68e2 11.0 landed
-
Add a WAIT option to DROP_REPLICATION_SLOT
- 8ba6d50f923b 10.0 landed
- be7161566db2 11.0 landed
-
Fix race conditions in replication slot operations
- 9915de6c1cb2 10.0 cited