On Mon, Nov 05, 2012 at 04:42:56PM -0500, Bruce Momjian wrote: > On Mon, Nov 5, 2012 at 04:39:27PM -0500, Robert Haas wrote: > > On Mon, Nov 5, 2012 at 4:33 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> > > wrote: > > > AFAIR any transaction that modifies catalogs gets sync commit forcibly, > > > regardless of the setting. And sync commit means you get to wait for > > > all previous transactions to be flushed as well. So simply creating a > > > temp table ought to do the trick ...
SET synchronous_commit = on; SELECT txid_current(); Should be enough. > > I don't think there's a carve-out for system tables ... but creating a > > temp table with synchronous_commit=on will certainly do the trick. > > What is a temp table writing to WAL? The pg_class/pg_attribute changes? Yes. Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
