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 <alvherre(at)2ndquadrant(dot)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;
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?
In response to
pgsql-hackers by date
|Next:||From: Jeff Janes||Date: 2012-11-05 22:14:16|
|Subject: Re: Pg_upgrade speed for many tables|
|Previous:||From: Magnus Hagander||Date: 2012-11-05 21:54:23|
|Subject: Re: Deprecations in authentication|