Re: pg_dump --snapshot - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: pg_dump --snapshot
Date
Msg-id CA+U5nMKJz8404hy8hWrU-pdz4XPMBf6UtRnCF1fR0+Z0ZUUjmw@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump --snapshot  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pg_dump --snapshot  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_dump --snapshot  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 6 May 2013 19:35, Stephen Frost <sfrost@snowman.net> wrote:

> It certainly sounds interesting and I like the idea of it, but perhaps
> we need a different mechanism than just passing in a raw snapshot, to
> address the concerns that Tom raised.

It does *not* pass in a raw snapshot. All it does is to allow pg_dump
to use an API that is already exposed by the backend for this very
purpose, one that has been in Postgres since 9.2.
http://www.postgresql.org/docs/devel/static/functions-admin.html#FUNCTIONS-SNAPSHOT-SYNCHRONIZATION

Minor patch, no amazing new functionality, no drama.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] add long options to pgbench (submission 1)
Next
From: Simon Riggs
Date:
Subject: Re: pg_dump --snapshot