From: Christopher Browne <cbbrowne@ca.afilias.info>
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Fri, 28 Jan 2005 14:49:29 -0500
Message-ID: <60k6pxcp12.fsf@dba2.int.libertyrms.com> (raw)
References: <200501201503.31241.herve@elma.fr>
<41EFBF05.6000509@familyhealth.com.au>
<200501201536.08656.herve@elma.fr>
<1106236978.35299.496.camel@home>
<1106522910.5790.1.camel@fuji.krosing.net>
<20050128153620.GE9076@phlogiston.dyndns.org>
ajs@crankycanuck.ca (Andrew Sullivan) writes:
> On Mon, Jan 24, 2005 at 01:28:29AM +0200, Hannu Krosing wrote:
>>
>> IIRC it hates pg_dump mainly on master. If you are able to run pg_dump
>> from slave, it should be ok.
>
> For the sake of the archives, that's not really a good idea. There
> is some work afoot to solve it, but at the moment dumping from a
> slave gives you a useless database dump.
That overstates things a tad; I think it's worth elaborating on a bit.
There's a problem with the results of dumping the _schema_ from a
Slony-I 'subscriber' node; you want to get the schema from the origin
node. The problem has to do with triggers; Slony-I suppresses RI
triggers and such like on subscriber nodes in a fashion that leaves
the dumped schema a bit broken with regard to triggers.
But there's nothing wrong with the idea of using "pg_dump --data-only"
against a subscriber node to get you the data without putting a load
on the origin. And then pulling the schema from the origin, which
oughtn't be terribly expensive there.
--
"cbbrowne","@","ca.afilias.info"
<http://dev6.int.libertyrms.com/;
Christopher Browne
(416) 673-4124 (land)
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: cbbrowne@ca.afilias.info
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <60k6pxcp12.fsf@dba2.int.libertyrms.com>
* 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