X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 9C90711F66D3 for ; Wed, 19 Apr 2006 05:52:57 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 required=5 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id 1AXP16TTYgf3 for ; Wed, 19 Apr 2006 05:52:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id DB94E11F644A for ; Wed, 19 Apr 2006 05:52:48 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id k3J8qiwc010561 for ; Wed, 19 Apr 2006 05:52:45 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id k3J8q1aC007857 for pgsql-admin@postgresql.org; Wed, 19 Apr 2006 05:52:01 -0300 (ADT) (envelope-from news) From: "jayati.biswas@cmcltd.com" X-Newsgroups: pgsql.admin Subject: recovery problem Date: 19 Apr 2006 01:51:59 -0700 Organization: http://groups.google.com Lines: 33 Message-ID: <1145436719.720424.141380@i39g2000cwa.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Complaints-To: groups-abuse@google.com User-Agent: G2/0.2 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/48 (like Gecko) Safari/48,gzip(gfe),gzip(gfe) X-HTTP-Via: 1.1 sdns.cmc.net.in:3128 (squid/2.5.STABLE3) Complaints-To: groups-abuse@google.com Injection-Info: i39g2000cwa.googlegroups.com; posting-host=203.197.96.132; posting-account=9Cq7qA0AAACWm0pIDEGjulPzVg7w5KSX To: pgsql-admin@postgresql.org X-Archive-Number: 200604/234 X-Sequence-Number: 21403 hello, I am trying to setup a "hot standby" on a second machine. I have created a "recovery.conf" file and started a restore with logs from the primary machine. everything was OK. now a have new transaction logs generated by the primary machine and I want to "play" them on the secondary one. I have stopped postgres, recreated "recovery.conf", started postgres and I get the following error: ---------------------------------------------------------------- LOG: database system was shut down at 2005-05-23 05:19:34 PDT LOG: starting archive recovery LOG: restore_command = "/usr/cbmp/core/bin/restore_pg_tlog %f %p" LOG: restored log file "0000000100000008000000C4" from archive LOG: invalid resource manager ID 53 at 8/C4FFFEF8 LOG: invalid primary checkpoint record LOG: restored log file "0000000100000008000000C4" from archive LOG: invalid resource manager ID 52 at 8/C4FFFEBC LOG: invalid secondary checkpoint record PANIC: could not locate a valid checkpoint record LOG: startup process (PID 18297) was terminated by signal 6 LOG: aborting startup due to startup process failure LOG: logger shutting down ---------------------------------------------------------------- what is the procedure for creating a "hot standby" (continuously feeding a series of WAL files created by the primary machine into the secondary one) ?