| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Joachim Wieland <joe(at)mcknight(dot)de> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: synchronized snapshots |
| Date: | 2011-08-15 07:40:34 |
| Message-ID: | CA+U5nMKGf6CvamjE0+K-BqJ_LeFqts7a1x6W_Q6b8A8dD0h7Yg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 15, 2011 at 2:31 AM, Joachim Wieland <joe(at)mcknight(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-08-15 07:47:45 | Re: synchronized snapshots |
| Previous Message | daveg | 2011-08-15 07:27:36 | Re: error: could not find pg_class tuple for index 2662 |