| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Florent Guiliani <florent(at)guiliani(dot)fr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Retrieve the snapshot's LSN |
| Date: | 2015-07-16 17:08:48 |
| Message-ID: | CA+Tgmoa286s8VrmoODaxPZRaTjXonKrd_tAouHqO4+LykcBe=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 16, 2015 at 12:54 PM, Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-07-16 17:13:43 | Re: Retrieve the snapshot's LSN |
| Previous Message | Robert Haas | 2015-07-16 17:07:55 | Re: RFC: replace pg_stat_activity.waiting with something more descriptive |