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

Re: VACUUMs take twice as long across all nodes

From: Andreas Kostyrka <andreas(at)kostyrka(dot)org>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: VACUUMs take twice as long across all nodes
Date: 2006-10-29 17:12:09
Message-ID: 1162141929.7606.4.camel@andi-lap (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Am Sonntag, den 29.10.2006, 11:43 -0500 schrieb Andrew Sullivan:
> On Sun, Oct 29, 2006 at 05:24:33PM +0100, Andreas Kostyrka wrote:
> > Actually, you need to get the schema from the master node, and can take
> > the data from a slave. In mixing dumps like that, you must realize that
> > there are two seperate parts in the schema dump: "table definitions" and
> > "constraints". Do get a restorable backup you need to put the table
> > definitions stuff before your data, and the constraints after the data
> > copy.
> This will work, yes, but you don't get a real point-in-time dump this
But one does, because one can dump all data in one pg_dump call. And
with slony enabled, schema changes won't happen by mistake, they tend to
be a thing for the Slony High Priest, nothing for mere developers ;)


In response to

pgsql-performance by date

Next:From: Simon RiggsDate: 2006-10-30 08:18:21
Subject: Re: partitioned table performance
Previous:From: Andrew SullivanDate: 2006-10-29 16:43:19
Subject: Re: VACUUMs take twice as long across all nodes

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