From: | Simone Gotti <simone(dot)gotti(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | [PATCH] Fix drop replication slot blocking instead of returning error |
Date: | 2017-08-24 13:38:20 |
Message-ID: | CAEvsy6Wgdf90O6pUvg2wSVXL2omH5OPC-38OD4Zzgk-FXavj3Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Thanks,
Simone.
--
after git commit 9915de6c1cb calls to pg_drop_replication_slot or the
replication protocol DROP_REPLICATION_SLOT command will block when a
slot is in use instead of returning an error as before (as the doc
states).
This patch will set nowait to true to restore the previous
behavior.
Attachment | Content-Type | Size |
---|---|---|
fix_drop_replication_slot_blocking.patch | text/x-patch | 910 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2017-08-24 13:49:04 | Re: Update low-level backup documentation to match actual behavior |
Previous Message | Maksim Milyutin | 2017-08-24 13:08:56 | Re: auto_explain : log queries with wrong estimation |