X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A2FCA3A60D7 for ; Fri, 28 Jan 2005 20:04:10 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 95859-06 for ; Fri, 28 Jan 2005 20:04:06 +0000 (GMT) Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2ADD63A6065 for ; Fri, 28 Jan 2005 20:04:07 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id C9DBF31DA1; Fri, 28 Jan 2005 21:04:06 +0100 (MET) From: Christopher Browne X-Newsgroups: pgsql.performance Subject: Re: PostgreSQL clustering VS MySQL clustering Date: Fri, 28 Jan 2005 14:49:29 -0500 Organization: Afilias Canada - Operations Group Lines: 27 Message-ID: <60k6pxcp12.fsf@dba2.int.libertyrms.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Corporate Culture, linux) Cancel-Lock: sha1:R4bPywuR/szsGOYo/PAEAg0GDBE= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.043 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/596 X-Sequence-Number: 10286 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" Christopher Browne (416) 673-4124 (land)