Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id D8C9E29F0D5 for ; Mon, 12 Mar 2012 12:47:12 -0300 (ADT) Received: from sam.nabble.com ([216.139.236.26]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S77Sl-0005wu-2t for pgsql-performance@postgresql.org; Mon, 12 Mar 2012 15:47:11 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1S77SX-0000cz-Hr for pgsql-performance@postgresql.org; Mon, 12 Mar 2012 08:46:53 -0700 Date: Mon, 12 Mar 2012 08:46:53 -0700 (PDT) From: ddgs To: pgsql-performance@postgresql.org Message-ID: <1331567213547-5558198.post@n5.nabble.com> In-Reply-To: <4F5DC49D02000025000460F6@gw.wicourts.gov> References: <1331307029713-5550894.post@n5.nabble.com> <4F5DC49D02000025000460F6@gw.wicourts.gov> Subject: Re: count on transaction ID MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 0.9 (/) X-Archive-Number: 201203/93 X-Sequence-Number: 46543 It is just a simple idea syntax, not the exact one. Anyway, I am wonder how to get the 2^31 transaction IDs to cause the failure But I get the wraparound error warning when I delete a large no. of rows. So the wraparound failure is due to what reason, that I still have no idea (at least not the transaction limit, I guess) -- View this message in context: http://postgresql.1045698.n5.nabble.com/count-on-transaction-ID-tp5550894p5558198.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.