| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Create subscription with `create_slot=false` and incorrect slot name |
| Date: | 2017-05-30 19:01:05 |
| Message-ID: | 8447691d-99b4-3df2-9071-4ed81cff7596@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/25/17 17:26, Peter Eisentraut wrote:
> Another way to fix this particular issue is to not verify the
> replication slot name before doing the drop. After all, if the name is
> not valid, then you can also just report that it doesn't exist.
Here is a possible patch along these lines.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Remove-replication-slot-name-check-from-ReplicationS.patch | text/plain | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-05-30 19:02:55 | Re: Re: Create subscription with `create_slot=false` and incorrect slot name |
| Previous Message | Peter Eisentraut | 2017-05-30 18:13:52 | Re: Re: pg_dump ignoring information_schema tables which used in Create Publication. |