Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id AD21E2E0063 for ; Sat, 21 Jun 2008 07:19:58 -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 91026-04 for ; Sat, 21 Jun 2008 07:19:51 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mx1.anaxanet.com (mx1.anaxanet.com [8.8.246.7]) by developer.postgresql.org (Postfix) with ESMTP id 327122E004B for ; Sat, 21 Jun 2008 07:19:54 -0300 (ADT) Received: from c-68-45-8-154.hsd1.nj.comcast.net [68.45.8.154] by mx1.anaxanet.com with SMTP; Sat, 21 Jun 2008 04:16:05 -0600 From: "Bill Bartlett" To: Subject: PG 8.0.4 - Does Dump + drop_db + reload reset XID to prevent wraparound? Date: Sat, 21 Jun 2008 06:19:30 -0400 Message-ID: <001401c8d388$4b5d0720$e2171560$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcjTUjXsi4lcs+pnQ+y0QBGRdsvq5A== Content-Language: en-us X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/188 X-Sequence-Number: 29526 In a PostgreSQL 8.0.4 environment, does dropping the database and reloading it completely reset the XID information that causes transaction ID wraparound? (I am assuming that it does, but wanted to double-check before doing this.)