Re: Replication identifiers, take 4 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Replication identifiers, take 4
Date
Msg-id 55403B2D.8040401@gmx.net
Whole thread Raw
In response to Re: Replication identifiers, take 4  (Andres Freund <andres@anarazel.de>)
Responses Re: Replication identifiers, take 4
List pgsql-hackers
On 4/24/15 4:29 PM, Andres Freund wrote:
>> Shouldn't this be backed up by pg_dump(all?)?
> 
> Given it deals with LSNs and is, quite fundamentally due to concurrency, non transactional, I doubt it's worth it.
Theother side's slots also aren't going to be backed up as pg dump obviously can't know about then. So the represented
datawon't make much sense.
 

I agree it might not be the best match.  But we should consider that we
used to say, a backup by pg_dumpall plus configuration files is a
complete backup.  Now we have replication slots and possibly replication
identifiers and maybe similar features in the future that are not
covered by this backup method.



pgsql-hackers by date:

Previous
From: Dave Jones
Date:
Subject: Re: Temporal extensions
Next
From: Tom Lane
Date:
Subject: Re: shared_libperl, shared_libpython