Re: Pg_upgrade speed for many tables - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Pg_upgrade speed for many tables
Date
Msg-id CA+Tgmoai8iTfb2t1yUXtnTu3moQORK3NvUsKQ4YqsE8CpqpH5w@mail.gmail.com
Whole thread Raw
In response to Re: Pg_upgrade speed for many tables  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Pg_upgrade speed for many tables  (Bruce Momjian <bruce@momjian.us>)
Re: Pg_upgrade speed for many tables  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On Mon, Nov 5, 2012 at 4:07 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> Or have options for pg_dump and pg_restore to insert "set
> synchronous_commit=off" into the SQL stream?

It would be kind of neat if we had a command that would force all
previously-asynchronous commits to complete.  It seems likely that
very, very few people would care about intermediate pg_dump states, so
we could do the whole dump asynchronously and then do "FORCE ALL
COMMITS;" or whatever at the end.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Pg_upgrade speed for many tables
Next
From: Robert Haas
Date:
Subject: Re: Doc patch, distinguish sections with an empty row in error code table