Re: How to lose transaction history (xmin values, WAL, etc.)?

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Richard Walker <richard(at)softimp(dot)com(dot)au>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to lose transaction history (xmin values, WAL, etc.)?
Date: 2010-05-20 16:39:48
Message-ID: 1274373556-sup-1171@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Excerpts from Richard Walker's message of jue may 20 02:19:17 -0400 2010:

> (a) (ii) It seems a breach is possible via the xmin values.
> In that case, what about doing updates inside a transaction
> that does a trivial update of all rows, e.g.:
> begin transaction;
> update mytable ....; -- change one row
> update mytable set id=id; -- change all rows
> commit;
> So now all rows have the same xmin values.
> Does this work? Performance is not so good, is it?
> Is there a better way?

The easiest way to do this is probably VACUUM FREEZE.

--

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Matt Bartolome 2010-05-20 17:43:26 postgres startup failure
Previous Message Ashley Sheridan 2010-05-20 16:26:27 Re: [PHP] Some undefined function errors