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 0E3C08B9CFD for ; Sun, 6 Feb 2005 23:06:42 +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 66516-08 for ; Sun, 6 Feb 2005 23:06:25 +0000 (GMT) Received: from smtp111.mail.sc5.yahoo.com (smtp111.mail.sc5.yahoo.com [66.163.170.9]) by svr1.postgresql.org (Postfix) with SMTP id 855378B9E06 for ; Sun, 6 Feb 2005 23:06:26 +0000 (GMT) Received: from unknown (HELO jupiter.black-lion.info) (janwieck@68.80.245.191 with login) by smtp111.mail.sc5.yahoo.com with SMTP; 6 Feb 2005 23:06:26 -0000 Received: from [172.21.8.128] ([192.168.192.101]) (authenticated bits=0) by jupiter.black-lion.info (8.12.10/8.12.9) with ESMTP id j16N69L3026052; Sun, 6 Feb 2005 18:06:14 -0500 (EST) (envelope-from JanWieck@Yahoo.com) Message-ID: <4206A2DB.70102@Yahoo.com> Date: Sun, 06 Feb 2005 18:06:03 -0500 From: Jan Wieck User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christopher Browne Cc: pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering 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> <60k6pxcp12.fsf@dba2.int.libertyrms.com> In-Reply-To: <60k6pxcp12.fsf@dba2.int.libertyrms.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.322 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200502/104 X-Sequence-Number: 10433 On 1/28/2005 2:49 PM, Christopher Browne wrote: > 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. And there is a script in the current CVS head that extracts the schema from the origin in a clean, slony-traces-removed state. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #