X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 99AE911F644F for ; Thu, 20 Apr 2006 19:43:22 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.291 X-Spam-Level: X-Spam-Status: No, score=0.291 required=5 tests=[AWL=0.291] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id kiKaY-nhZgG6 for ; Thu, 20 Apr 2006 19:43:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 6877811F6311 for ; Thu, 20 Apr 2006 19:43:18 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 9970B56431; Thu, 20 Apr 2006 17:43:18 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Thu, 20 Apr 2006 17:43:17 -0500 Date: Thu, 20 Apr 2006 17:43:17 -0500 From: "Jim C. Nasby" To: Sriram Dandapani Cc: pgsql-admin@postgresql.org Subject: Re: WAL file naming after postmaster restart Message-ID: <20060420224317.GO49405@pervasive.com> References: <6992E470F12A444BB787B5C937B9D4DF03EF4766@ca-mail1.cis.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF03EF4766@ca-mail1.cis.local> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060420:sdandapani@counterpane.com::9KCz+DjJryLSaCtF:00000000000 0000000000000000000000003rsg X-Hashcash: 1:20:060420:pgsql-admin@postgresql.org::w5cKNY5dPh0zTlKC:00000000000 00000000000000000000000073or X-Archive-Number: 200604/204 X-Sequence-Number: 21373 On Wed, Apr 12, 2006 at 11:05:52AM -0700, Sriram Dandapani wrote: > I noticed something strange. When postgres crashed and restarted...the > archived WAL log file numbering did not take off from where it left > off..instead a new sequence was started (the new sequence was higher > than the last one before crashing)..Is this the expected behaviour on > postmaster crash and auto-recover. (I did not do a manual recovery with > the recover.conf) I'm not sure why one should care about this, but AFAIK it's normal. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461