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

Re: Pg_upgrade speed for many tables

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>,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 22:03:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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;
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?



In response to

pgsql-hackers by date

Next:From: Jeff JanesDate: 2012-11-05 22:14:16
Subject: Re: Pg_upgrade speed for many tables
Previous:From: Magnus HaganderDate: 2012-11-05 21:54:23
Subject: Re: Deprecations in authentication

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