| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Ludovic Vaugeois-Pepin <ludovicvp(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists |
| Date: | 2017-05-31 18:39:31 |
| Message-ID: | CAB7nPqQXRwWpfo7g=0-qgH4ku2xY4nRB8sk-kBLtRj4_=GYpKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wed, May 31, 2017 at 11:18 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2017-05-31 18:22:18 +0200, Magnus Hagander wrote:
>> However, the client can't access the pid of the server as it is now,
>> and its the client that has to create the name.
>
> I don't think that's actually true? Doesn't the wire protocol always
> include the PID, which is then exposed with PQbackendPID()?
Ah, you are right here. I forgot that this is exposed to the client at
backend startup.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-05-31 18:57:18 | Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists |
| Previous Message | Andres Freund | 2017-05-31 18:18:01 | Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-05-31 18:57:18 | Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists |
| Previous Message | Stephen Frost | 2017-05-31 18:36:16 | Re: TAP backpatching policy |