Re: Including replication slot data in base backups

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Including replication slot data in base backups
Date: 2014-04-14 16:55:35
Message-ID: CA+Tgmoamk99hNjog+ksQ+eJf6-+yjrMxh1DEzSq72psZiHyJXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 14, 2014 at 9:26 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> This makes me think that it's safer to just remove replication slot files
> at the beginning of the recovery when both backup_label and recovery.conf
> exist.

Well, we could do that, but that would preempt anyone who *does* want
to keep those replication slots around. I'm not sure that's a good
idea, either.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-04-14 17:01:42 Re: Signaling of waiting for a cleanup lock?
Previous Message Andres Freund 2014-04-14 16:53:57 Re: Signaling of waiting for a cleanup lock?