On Tuesday 18 November 2008 16:46:23 Alvaro Herrera wrote:
Arctic Toucan wrote:
If I know that there are no more inserts going into those
partitioned tables, can I do a bulk change of their relfrozenxids
setting them back 500million transactions without causing problems?
This will mean
I have a heavily partitioned DW type database that has over 5,000 tables in it.
Data is only ever inserted, read and then truncated after some period of time.
Once the table is truncated, the constraints are changed and the table is
reused. This works well until Postgres hits the
Arctic Toucan wrote:
I have a heavily partitioned DW type database that has over 5,000
tables in it. Data is only ever inserted, read and then truncated
after some period of time. Once the table is truncated, the
constraints are changed and the table is reused. This works well until
Alvaro Herrera [EMAIL PROTECTED] writes:
AFAICS this should be safe. In fact, in 8.3 TRUNCATE advances
relfrozenxid. (Perhaps you should consider upgrading if possible.)
...
Tou could just obtain the xid of the transaction that's going to do the
import (for example by creating a temp table
PROTECTED] CC: [EMAIL PROTECTED]; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Is it safe to reset relfrozenxid without using vacuum?
Date: Tue, 18 Nov 2008 13:07:16 -0500 From: [EMAIL PROTECTED] Alvaro
Herrera [EMAIL PROTECTED] writes: AFAICS this should be safe. In fact,
in 8.3 TRUNCATE
Arctic Toucan wrote:
If I know that there are no more inserts going into those
partitioned tables, can I do a bulk change of their relfrozenxids
setting them back 500million transactions without causing problems?
This will mean that the relfrozenxid is not representative of the row
versions,
