| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump --snapshot |
| Date: | 2013-05-06 17:58:45 |
| Message-ID: | CA+U5nM+xi35JR8H7jLP0gj14VSskbQvyGWNNHe6afBTzQOS6uA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6 May 2013 18:07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Or in short: -1 for the very concept of letting the user control
> pg_dump's snapshot.
That API is already exposed, so not sure why you say this now? This
has been in PG since early in 9.2, about 2 years ago.
In any case, "flashback database" is one of the most requested
features I know of... the ability to dump the database as it appeared
in the past *after* that point has passed. I call it by its name as
used in Oracle, but many people have taken the trouble to describe
that in detail to me, even without knowing a similar feature existed
elsewhere.
So it will always be important to do SET TRANSACTION SNAPSHOT 'a point
in the past'
and if we can do that, why not pg_dump also?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-05-06 18:35:14 | Re: pg_dump --snapshot |
| Previous Message | Andres Freund | 2013-05-06 17:23:56 | Re: pg_dump --snapshot |