Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V9cQr-0000YW-Hg for pgsql-admin@arkaria.postgresql.org; Wed, 14 Aug 2013 14:52:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1V9cQr-0003Wf-18 for pgsql-admin@arkaria.postgresql.org; Wed, 14 Aug 2013 14:52:17 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V9cQp-0003UJ-Jb for pgsql-admin@postgresql.org; Wed, 14 Aug 2013 14:52:15 +0000 Received: from internet06.ebureau.com ([65.127.24.25]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V9cQk-0007KE-Cd for pgsql-admin@postgresql.org; Wed, 14 Aug 2013 14:52:14 +0000 Received: from localhost (localhost [127.0.0.1]) by internet06.ebureau.com (Postfix) with ESMTP id A1AA2397A8E1 for ; Wed, 14 Aug 2013 09:52:09 -0500 (CDT) X-Virus-Scanned: amavisd-new at ebureau.com Received: from internet06.ebureau.com ([127.0.0.1]) by localhost (internet06.ebureau.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id piMAb1WpY3B5 for ; Wed, 14 Aug 2013 09:52:08 -0500 (CDT) Received: from punch.office.ebureau.com (punch.office.ebureau.com [10.10.20.24]) by internet06.ebureau.com (Postfix) with ESMTPSA id D957E397A8D2 for ; Wed, 14 Aug 2013 09:52:08 -0500 (CDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: vacuum freeze performance, wraparound issues From: Natalie Wenz In-Reply-To: <5056.1376367324@sss.pgh.pa.us> Date: Wed, 14 Aug 2013 09:52:08 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <55CAE74F-D466-40B9-A4EA-7326778E3783@ebureau.com> References: <273F3E90-053B-4137-BE4D-3E7115A6A12E@ebureau.com> <5056.1376367324@sss.pgh.pa.us> To: "pgsql-admin@postgresql.org" X-Mailer: Apple Mail (2.1508) X-Pg-Spam-Score: -2.8 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Yes, absolutely! We would dump and reload all of our large databases in a h= eartbeat if there were an option for a 64-bit xid!=20 Another quick question: When this database took itself offline to avoid tra= nsaction id wraparound, we opted for a vacuum freeze in single-user mode. W= as that the right choice? In other words, what is the fastest way to get a = database back online when this occurs? Maybe a plain vacuum would have been= better?=20 Thanks! Natalie On Aug 12, 2013, at 11:15 PM, Tom Lane wrote: > Natalie Wenz writes: >> ... With the speed postgres is capable of, and the ever-falling prices >> of storage making larger, faster databases possible, has the possibility >> of changing the transaction id to a 64-bit (or even 128-bit!) value been >> considered? >=20 > Not terribly seriously --- the penalties from making row headers 8 bytes > bigger have always seemed to outweigh the advantages. (128 bits is right > out; we don't even have 128-bit LSNs.) >=20 > We'd probably take a patch to make 64-bit XIDs available as a compile-time > option, if someone wanted to do the legwork to write and test it. But > let me ask you this: if such an option existed, would you be willing to > dump and reload your database to take advantage of it? The conversion > costs of changing row header format seem like they'd discourage exactly > those people whom such a feature could help. >=20 > regards, tom lane >=20 >=20 > --=20 > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin