Curious why autovacuum does not handle this problem. Here are my
settings
max_fsm_pages = 2000000
autovacuum = on # enable autovacuum
autovacuum_naptime = 300 # time between autovacuum runs,
in
autovacuum_vacuum_threshold = 10000 # min # of tuple updates before
# vacuum
autovacuum_analyze_threshold = 1500 # min # of tuple updates before
# analyze
autovacuum_vacuum_scale_factor = 0.4 # fraction of rel size before
# vacuum
autovacuum_analyze_scale_factor = 0.2 # fraction of rel size before
# analyze
autovacuum_vacuum_cost_delay = 100
autovacuum_vacuum_cost_limit = 1000
The database has a constant rate of about 50-100G a day of data flowing
in which gets deleted after 2 days.(this cycle keeps repeating). There
are historical tables that grow at a rate of 2G-4G a day
-----Original Message-----
From: Scott Marlowe [mailto:smarlowe@g2switchworks.com]
Sent: Wednesday, September 06, 2006 12:38 PM
To: Sriram Dandapani
Cc: Tom Lane; pgsql-admin@postgresql.org
Subject: RE: [ADMIN] transactoin id wraparound problem
On Wed, 2006-09-06 at 14:23, Sriram Dandapani wrote:
> Thanks
>
> Is there a way to monitor vacuum progress. Can I resume normal
> operations assuming vacuum will update the transaction ids or should I
> wait till it finishes.
As Andrew mentioned, there's the possibility of wrapping before vacuum
finishes. Other than that, there's no danger to continuing to use the
db while it's being vacuumed.
There was a post here a little while back that had a query that would
show you how many transactions you had until wraparound and which
databases had been vacuumed when...
The basic data is in pg_database. Take a look at that table.
