Re: synchronized snapshots - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: synchronized snapshots
Date
Msg-id CA+U5nMKGf6CvamjE0+K-BqJ_LeFqts7a1x6W_Q6b8A8dD0h7Yg@mail.gmail.com
Whole thread Raw
In response to synchronized snapshots  (Joachim Wieland <joe@mcknight.de>)
Responses Re: synchronized snapshots
Re: synchronized snapshots
Re: synchronized snapshots
Re: synchronized snapshots
Re: synchronized snapshots
List pgsql-hackers
On Mon, Aug 15, 2011 at 2:31 AM, Joachim Wieland <joe@mcknight.de> wrote:

> In short, this is how it works:
>
> SELECT pg_export_snapshot();
>  pg_export_snapshot
> --------------------
>  000003A1-1
> (1 row)
>
>
> (and then in a different session)
>
> BEGIN TRANSACTION ISOLATION LEVEL REPEATABLE READ (SNAPSHOT = '000003A1-1');

I don't see the need to change the BEGIN command, which is SQL
Standard. We don't normally do that.

If we have pg_export_snapshot() why not pg_import_snapshot() as well?

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: daveg
Date:
Subject: Re: error: could not find pg_class tuple for index 2662
Next
From: Heikki Linnakangas
Date:
Subject: Re: synchronized snapshots