Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists

From: Andres Freund <andres(at)anarazel(dot)de>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: 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:18:01
Message-ID: 20170531181801.llmz5arlmmzoedi2@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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()?

- Andres

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2017-05-31 18:39:31 Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists
Previous Message Michael Paquier 2017-05-31 18:09:55 Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-05-31 18:20:13 Re: Error while creating subscription when server is running in single user mode
Previous Message Michael Paquier 2017-05-31 18:09:55 Re: Re: [GENERAL] pg_basebackup error: replication slot "pg_basebackup_2194" already exists