Using COPY FREEZE with pg_restore --single-transaction
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?
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 25 January 2013 15:24, Bruce Momjian <bruce@momjian.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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers