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 853B711F66BE for ; Fri, 21 Apr 2006 00:10:06 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.122 X-Spam-Level: X-Spam-Status: No, score=0.122 required=5 tests=[AWL=0.122] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id SYuz2ovM4oYN for ; Fri, 21 Apr 2006 00:10:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 8895711F68C6 for ; Fri, 21 Apr 2006 00:10:01 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k3L39wpO002765; Thu, 20 Apr 2006 23:09:58 -0400 (EDT) To: "Benjamin Krajmalnik" cc: pgsql-admin@postgresql.org Subject: Re: Howto: Using PITR recovery for standby replication In-reply-to: <8511B4970E0D124898E973DF496F9B4357E0F4@stash.stackdump.local> References: <443F9BF3.4060101@laposte.net> <1145028323.5597.1.camel@localhost.localdomain> <443FDF05.4060600@laposte.net> <20060421014243.GR49405@pervasive.com> <8511B4970E0D124898E973DF496F9B4357E0F4@stash.stackdump.local> Comments: In-reply-to "Benjamin Krajmalnik" message dated "Thu, 20 Apr 2006 20:58:51 -0600" Date: Thu, 20 Apr 2006 23:09:58 -0400 Message-ID: <2764.1145588998@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200604/211 X-Sequence-Number: 21380 "Benjamin Krajmalnik" writes: > I have tried using pg_dump, but discovered that the backup was not a = > consistent backup. Really? > Back to the problem I faced when testing backups with pg_dump, it = > appears that the backup was not a consistent backup of the data. For = > example, sequences which are used by some tables bo longer held the = > correct values (the tables now held higher values), Sequences are non-transactional, so pg_dump might well capture a higher value of the sequence counter than is reflected in any table row, but there are numerous other ways by which a gap can appear in the set of sequence values. That's not a bug. If you've got real discrepancies in pg_dump's output, a lot of us would like to know about 'em. regards, tom lane