pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Natalie Wenz <nataliewenz@ebureau.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: vacuum freeze performance, wraparound issues
Date: Wed, 14 Aug 2013 09:52:08 -0500
Message-ID: <55CAE74F-D466-40B9-A4EA-7326778E3783@ebureau.com> (raw)
In-Reply-To: <5056.1376367324@sss.pgh.pa.us>
References: <273F3E90-053B-4137-BE4D-3E7115A6A12E@ebureau.com>
	<5056.1376367324@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Yes, absolutely! We would dump and reload all of our large databases in a heartbeat if there were an option for a 64-bit xid! 

Another quick question: When this database took itself offline to avoid transaction id wraparound, we opted for a vacuum freeze in single-user mode. Was 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? 

Thanks!
Natalie


On Aug 12, 2013, at 11:15 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Natalie Wenz <nataliewenz@ebureau.com> 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?
> 
> 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.)
> 
> 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.
> 
> 			regards, tom lane
> 
> 
> -- 
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin



-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (3+ messages)

Message-ID: <55CAE74F-D466-40B9-A4EA-7326778E3783@ebureau.com>
Permalink:  ../55CAE74F-D466-40B9-A4EA-7326778E3783@ebureau.com/
Also on:    postgresql.org/message-id/55CAE74F-D466-40B9-A4EA-7326778E3783@ebureau.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: nataliewenz@ebureau.com
  Subject: Re: vacuum freeze performance, wraparound issues
  In-Reply-To: <55CAE74F-D466-40B9-A4EA-7326778E3783@ebureau.com>
  References: <273F3E90-053B-4137-BE4D-3E7115A6A12E@ebureau.com> <5056.1376367324@sss.pgh.pa.us> <55CAE74F-D466-40B9-A4EA-7326778E3783@ebureau.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox