From: marc.hsiao <marc.hsiao@cobrasonic.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to turn autovacuum prevent wrap around run faster?
Date: Wed, 12 Jan 2011 16:21:12 +0800
Message-ID: <002d01cbb231$ac7a29e0$056e7da0$@hsiao@cobrasonic.com> (raw)
In-Reply-To: <002c01cbae42$ef48eec0$cddacc40$@hsiao@cobrasonic.com>
References: <-121201471744211051@unknownmsgid>
<AANLkTi=39eEqo-5j4DxGTLq4akygP2_Uh-+ZfAmf1MPJ@mail.gmail.com>
<000601cbaaea$28a5e120$79f1a360$@hsiao@cobrasonic.com>
<002c01cbae42$ef48eec0$cddacc40$@hsiao@cobrasonic.com>
Hi All:
My Server list below
postgres=# select version();
version
----------------------------------------------------------------------------
---------------------------------------
PostgreSQL 8.4.2 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC)
4.1.2 20080704 (Red Hat 4.1.2-44), 64-bit
(1 row)
I use another way to solve this issue.
The table is partition table, I will create this partition table before
insert data.
The freezemaxid will be smaller than others, so that the partition table
will be last one that been vacuum.
Use this sql to check
SELECT relname, age(relfrozenxid) FROM pg_class WHERE relkind = 'r' order by
2;
I also adjust the postgresql.conf three parameters.
This will cause that my partition table will not reach the max_age in a
short time.
autovacuum_freeze_max_age = 2000000000
vacuum_freeze_min_age = 10000000
vacuum_freeze_table_age = 150000000
As far as now that my partition table drop run normal, without autovacuum
prevent wraparound interrupt.
Regards
Marc
-----Original Message-----
From: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-owner@postgresql.org] On Behalf Of marc.hsiao
Sent: Friday, January 07, 2011 4:15 PM
To: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] How to turn autovacuum prevent wrap around run
faster?
Hi All:
The autovacuum (prevent wraparound) still run more than 36 hours, I can not
drop the partition table after adjust the autovacuum parameters.
If a table is running autovacuum (prevent wraparound), can I purge this
table?
If not, what else I can do for clean this partition table?
If the table is running autovacuum (prevent wraparound), can I use pg_dump
to backup it?
Will the Transaction ID Wraparound Failures happen while table has been
restored into new DB?
Regards
Marc
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: marc.hsiao@cobrasonic.com
Subject: Re: How to turn autovacuum prevent wrap around run faster?
In-Reply-To: <002d01cbb231$ac7a29e0$056e7da0$@hsiao@cobrasonic.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