pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andreas Kostyrka <andreas@kostyrka.org>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: VACUUMs take twice as long across all nodes
Date: Sun, 29 Oct 2006 18:12:09 +0100
Message-ID: <1162141929.7606.4.camel@andi-lap> (raw)
In-Reply-To: <20061029164319.GG14585@phlogiston.dyndns.org>
References: <20196.1161874041@sss.pgh.pa.us>
	<20061026160609.5e94e581.gdh@laterooms.com>
	<20061026191728.GD26892@nasby.net>
	<20061026213556.174bd7b5.gdh@laterooms.com>
	<20061026220937.GA6866@phlogiston.dyndns.org>
	<20061027102025.8183c5d9.gdh@laterooms.com>
	<20061029145825.GB14585@phlogiston.dyndns.org>
	<20061029150826.80afe324.gdh@laterooms.com>
	<20061029153404.GF14585@phlogiston.dyndns.org>
	<1162139073.7606.1.camel@andi-lap>
	<20061029164319.GG14585@phlogiston.dyndns.org>

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 ;)

Andreas

Attachments:

  signature.asc (application/pgp-signature, 188B) download

view thread (17+ messages)  latest in thread

Message-ID: <1162141929.7606.4.camel@andi-lap>
Permalink:  ../1162141929.7606.4.camel@andi-lap/
Also on:    postgresql.org/message-id/1162141929.7606.4.camel@andi-lap

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: andreas@kostyrka.org, ajs@crankycanuck.ca
  Subject: Re: VACUUMs take twice as long across all nodes
  In-Reply-To: <1162141929.7606.4.camel@andi-lap>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox