From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Using COPY FREEZE with pg_restore --single-transaction |
Date: | 2013-01-25 16:58:30 |
Message-ID: | CA+U5nM+XvkUu9ran+5cY=TWQquLTpvzte4KVMK=aDfbr-xfNXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 25 January 2013 15:24, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> pg_restore --single-transaction has the setup to make use of the new
> COPY FREEZE optimization.
>
> However, I don't see us using COPY FREEZE for pg_restore
> --single-transaction. Shouldn't we do that? The problem is we would
> need to have pg_dump emit the FREEZE, which would cause it not to load
> in earlier versions of Postgres, and to (soon) emit a NOTICE for
> non-single-transaction loads in all other cases. :-(
>
> Can pg_restore inject FREEZE itself when it does the copy?
I've added this as a discussion topic to the 9.3 Open Items, for
discussion after the CF.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-01-25 16:59:21 | Re: COPY FREEZE has no warning |
Previous Message | Dimitri Fontaine | 2013-01-25 16:58:07 | Re: Event Triggers: adding information |