On Mon, Nov 5, 2012 at 4:42 PM, Bruce Momjian <bruce(at)momjian(dot)us> 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 ...
>> 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?
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2012-11-05 21:54:23|
|Subject: Re: Deprecations in authentication|
|Previous:||From: Bruce Momjian||Date: 2012-11-05 21:42:56|
|Subject: Re: Pg_upgrade speed for many tables|