| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Better support of exported snapshots with pg_dump |
| Date: | 2014-09-01 08:25:58 |
| Message-ID: | 1BE0F00AB388000B75A8E7D7@eje.credativ.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On 1. September 2014 17:00:32 +0900 Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> Currently pg_dump does not allow a user to specify an exported snapshot
> name that he would like to use for a dump using SET TRANSACTION SNAPSHOT
> (now pg_export_snapshot is only used for parallel pg_dump within it). I
> imagine that this would be handy to take a consistent dump of a given
> database after creating a logical replication slot on it. Thoughts?
There was a discussion of this kind of feature some time ago here:
Not sure if all the arguments holds still true with the appearance of MVCC
catalog scans.
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Klyukin | 2014-09-01 08:39:59 | Re: implement subject alternative names support for SSL connections |
| Previous Message | Dave Page | 2014-09-01 08:15:12 | Re: What in the world is happening with castoroides and protosciurus? |