Re: Including replication slot data in base backups

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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-08 07:08:20
Message-ID: CAB7nPqR42HCxLzVW5NL0KUSddeCBCTj-7JdHbGEM8KRshJeBbg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 8, 2014 at 1:18 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Not sure if this is exactly the right way to do it, but I agree that
> something along those lines is a good idea. I also think, maybe even
> importantly, that we should probably document that people using
> file-copy based hot backups should strongly consider removing the
> replication slots by hand before using the backup.
Good point. Something here would be adapted in this case:
http://www.postgresql.org/docs/devel/static/backup-file.html
I am attaching an updated patch as well.
--
Michael

Attachment Content-Type Size
20140408_basebackup_slot_doc_v2.patch text/plain 1.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-04-08 08:49:04 Re: Why is it not sane to pass ExecStoreTuple(shouldFree=true) for tuples point into buffers
Previous Message Yugo Nagata 2014-04-08 07:01:24 Re: Fwd: Proposal: variant of regclass