| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Need Force flag for pg_drop_replication_slot() |
| Date: | 2015-05-29 19:21:05 |
| Message-ID: | 5568BC21.5090202@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/29/2015 12:08 PM, 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?
The client_addr?
JD
>
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-29 19:27:18 | Re: Need Force flag for pg_drop_replication_slot() |
| Previous Message | Joshua D. Drake | 2015-05-29 19:20:10 | Re: RFC: Remove contrib entirely |