From: | "Sriram Dandapani" <sdandapani(at)counterpane(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: transactoin id wraparound problem |
Date: | 2006-09-06 22:12:59 |
Message-ID: | 6992E470F12A444BB787B5C937B9D4DF05ABC8F6@ca-mail1.cis.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
stats_start_collector = on
#stats_command_string = off
#stats_block_level = off
stats_row_level = on
Yes...it is on.
I have other databases with similar data flow. Havent encountered this
issue yet (although I have to watch and vacuum manually to prevent such
errors)
Which option in the config file should I tweak to see autovacuum logging
entries?
Thanks
Sriram
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Wednesday, September 06, 2006 3:11 PM
To: Sriram Dandapani
Cc: Scott Marlowe; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] transactoin id wraparound problem
"Sriram Dandapani" <sdandapani(at)counterpane(dot)com> writes:
> Curious why autovacuum does not handle this problem. Here are my
> settings
> autovacuum = on # enable autovacuum
Do you have stats_row_level enabled? If not, autovac doesn't work.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sriram Dandapani | 2006-09-06 23:32:15 | Re: transactoin id wraparound problem |
Previous Message | Tom Lane | 2006-09-06 22:10:36 | Re: transactoin id wraparound problem |