X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 1EDE79FB2D3 for ; Sat, 29 Jul 2006 16:03:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 88379-09 for ; Sat, 29 Jul 2006 16:03:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 82AE39FB2D0 for ; Sat, 29 Jul 2006 16:03:11 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from ls405.htnet.hr (ls405.t-com.hr [195.29.150.135]) by svr4.postgresql.org (Postfix) with ESMTP id 4FB7B5AF026 for ; Sat, 29 Jul 2006 19:03:09 +0000 (GMT) Received: from ls422.t-com.hr (ls422.t-com.hr [195.29.150.237]) by ls405.htnet.hr (Postfix) with ESMTP id C3ABE144C40; Sat, 29 Jul 2006 21:00:23 +0200 (CEST) Received: from ls422.t-com.hr (localhost.localdomain [127.0.0.1]) by ls422.t-com.hr (Qmlai) with ESMTP id B47DAC90048; Sat, 29 Jul 2006 21:00:23 +0200 (CEST) X-Envelope-Sender: mario.splivalo@mobart.hr X-Envelope-Sender: mario.splivalo@mobart.hr Received: from 89-172-29-106.adsl.net.t-com.hr (89-172-29-106.adsl.net.t-com.hr [89.172.29.106])by ls422.t-com.hr (Qmlai) with ESMTP id 388941308032;Sat, 29 Jul 2006 21:00:14 +0200 (CEST) Subject: Re: Postgres replication solutions From: Mario Splivalo Reply-To: mario.splivalo@mobart.hr To: Jeff Frost Cc: pgsql-admin@postgresql.org In-Reply-To: References: <1154095881.18822.12.camel@localhost.localdomain> Content-Type: text/plain Organization: Mob-Art Date: Sat, 29 Jul 2006 20:59:59 +0200 Message-Id: <1154199599.18161.8.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit X-imss-version: 2.041 X-imss-result: Passed X-imss-scores: Clean:44.74469 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.88 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, SARE_SPEC_REPLICA, SPF_SOFTFAIL, UNPARSEABLE_RELAY X-Spam-Level: * X-Archive-Number: 200607/278 X-Sequence-Number: 22524 On Fri, 2006-07-28 at 11:01 -0700, Jeff Frost wrote: > Mario, > > There's also Command Prompt's Mammoth replicator: > http://commandprompt.com/products/mammothreplicator/ I sent an email asking if they have an evaluation version of some sort... > Also, you could batch up PITR restores or even just dump restores if the > timing was acceptable and you could afford the replicated DB to be down during > those batch updates. Dump restores are what we're using now, but we're soon going to have to abandon that approach. The dump/restore cycle takes around 20 minutes, and we're expecting rapid growth of the database. The another problem is that Tomcat won't release connections to postgres unless you stop it. PIRT restores are not working for me. I did it like this: I issued pg_start_backup, then I 'tar cvf - pg_data/ | nc destination 9876'-ed the cluster directory, when that was done i did pg_stop_backup, after that I deleted pg_xlog directory, and put new WAL files (created after backup begun) in directory specified in restore.conf. I started postgres, everything went ok. Postgres replayed wal files, and system was ready. Then, when new WAL files arrived, I shut down postgres, put WAL files in place, restarted postgres, but it complained, and didn't replay newly created wal files. It only does so when I 'recreate' original filesystem backup. > Another option is using pgpool's replication. I considered that too, but that adds another layer between the clients and postgres itself, and it allows for only two servers, and I realy don't need failover cluster capabilities. Mike