On Thu, Jul 16, 2015 at 12:54 PM, Andres Freund <andres@anarazel.de> wrote:
> Well, in combination with logical decoding it kinda has one: It should
> allow you to take a dump of the database with a certain snapshot and
> replay all transactions with a commit lsn bigger than the "snapshot's
> lsn" and end up with a continually consistent database.
>
> Visibility for HS actually works precisely in commit LSN order, even if
> that is possibly different than on the primary...
That makes sense, and hopefully answers Florent's question about why
this is only exposed through the slot mechanism.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
