Skip site navigation (1) Skip section navigation (2)

Re: Pg_upgrade speed for many tables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pg_upgrade speed for many tables
Date: 2012-11-05 21:50:42
Message-ID: CA+TgmobNkdKTF02dCYMnXgEGte3_r4ubDpp4efYi7BzHMf9=zw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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?

Yes.

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


In response to

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2012-11-05 21:54:23
Subject: Re: Deprecations in authentication
Previous:From: Bruce MomjianDate: 2012-11-05 21:42:56
Subject: Re: Pg_upgrade speed for many tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group