From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, sanyam jain <sanyamjain22(at)live(dot)in>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Use of snapshot in logical replication |
Date: | 2017-06-08 01:18:49 |
Message-ID: | 20170608011849.qwuhjikjcgjh2yro@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2017-06-08 03:14:55 +0200, Petr Jelinek wrote:
> On 08/06/17 03:08, Craig Ringer wrote:
> > On 7 June 2017 at 18:16, sanyam jain <sanyamjain22(at)live(dot)in> wrote:
> >> Hi,
> >>
> >> Can someone explain the usage of exporting snapshot when a logical
> >> replication slot is created?
> >
> > It's used to pg_dump the schema at a consistent point in history where
> > all xacts are known to be in the snapshot (and thus dumped) or known
> > not to be (so they'll be streamed out on the slot).
> >
>
> Not just schema, it can also be used to get existing data at consistent
> point in history so that changes will follow without gaps or duplicates.
>
> That being said, the built-in logical replication isn't using the
> exported snapshots at all.
Just because it uses them in the same session doesn't really change the
picture, that's more or less just an optimization. It's essentially
just a cheaper version of importing a snapshot that'd have to be
exported in same session.
- Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2017-06-08 01:19:01 | Re: Notes on testing Postgres 10b1 |
Previous Message | Petr Jelinek | 2017-06-08 01:14:55 | Re: Use of snapshot in logical replication |