| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Need Force flag for pg_drop_replication_slot() |
| Date: | 2015-05-29 19:42:14 |
| Message-ID: | 5568C116.6060608@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/29/2015 12:27 PM, Andres Freund wrote:
> On 2015-05-29 12:08:24 -0700, Josh Berkus wrote:
>> Now, BDR is good because it sets an application_name which lets me
>> figure out what's using the replication slot. But that's by no means
>> required; other LC plug-ins, I expect, do not do so. So there's no way
>> for the user to figure out which replication connection relates to which
>> slots, as far as I can tell.
>>
>> In this test, it's easy because there's only one replication connection
>> and one slot. But imagine the case of 14 replication connections with
>> their own slots. How could you possibly figure out which one was the
>> laggy one?
>
> 9.5 shows the pid.
OK, will test, thanks.
--Josh Berkus
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-29 19:43:01 | Re: [CORE] postpone next week's release |
| Previous Message | Stephen Frost | 2015-05-29 19:37:44 | Re: [CORE] postpone next week's release |