Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id C93AF2E0047 for ; Thu, 19 Jun 2008 20:52:30 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 96480-03 for ; Thu, 19 Jun 2008 20:52:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by developer.postgresql.org (Postfix) with ESMTP id E03632E0030 for ; Thu, 19 Jun 2008 20:52:27 -0300 (ADT) Received: from [192.168.1.5] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m5JNr7G5030105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Jun 2008 16:53:09 -0700 Subject: Re: Warm-standby in 8.2 From: "Joshua D. Drake" To: Bhella Paramjeet-PFCW67 Cc: pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain Organization: Command Prompt, Inc. Date: Thu, 19 Jun 2008 16:51:17 -0700 Message-Id: <1213919477.8492.14.camel@jd-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 19 Jun 2008 16:54:13 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/168 X-Sequence-Number: 29506 On Thu, 2008-06-19 at 19:31 -0400, Bhella Paramjeet-PFCW67 wrote: > Hi, > > We have created a postgres database with a warm-standby in postgres 8.2 > following the document on the archive by Charles Duffy. The standby > database is in continuous recovery mode and archived logs are synced to > the standby from primary, every 10 minutes. The primary and the standby > database are running fine but we need to monitor the standby database to > check that it is up, it is getting synced every 10 minutes, and that it > is not out of sync with primary database. What would be the best way to > make these checks or what processes to check to make sure that the > archived logs from primary database are continuously getting applied on > the standby database. > > There must be other people using this set up so just need advice on how > people are monitoring the standby database. Any suggestions or help will > be highly appreciated. If you set the logging to debug2 in the postgresql.conf on the standby, it will tell you what logs are being restored as they are restored. Further pg_standby will tell you in the process list. Joshua D. Drake > > Thanks > Paramjeet Bhella > >