Too many messages from Autovacuum

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: pgsql-patches(at)postgresql(dot)org
Subject: Too many messages from Autovacuum
Date: 2006-09-26 16:04:26
Message-ID: 1159286666.2696.27.camel@holly
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Recommending downgrade of these annoying messages from LOG to DEBUG1:

2006-09-23 15:57:56 EDT_3147 LOG: transaction ID wrap limit is 2147484170, limited by database "postgres"
2006-09-23 15:57:57 EDT_3147 LOG: transaction ID wrap limit is 2147484170, limited by database "postgres"
2006-09-23 15:59:59 EDT_3394 LOG: transaction ID wrap limit is 2147484170, limited by database "postgres"
2006-09-23 15:59:59 EDT_3394 LOG: transaction ID wrap limit is 2147484170, limited by database "postgres"
2006-09-23 16:02:04 EDT_3646 LOG: transaction ID wrap limit is 2147484170, limited by database "postgres"
2006-09-23 16:04:07 EDT_3892 LOG: transaction ID wrap limit is 2147484170, limited by database "postgres"
2006-09-23 16:04:08 EDT_3892 LOG: transaction ID wrap limit is 2147484170, limited by database "postgres"
2006-09-23 16:06:11 EDT_4138 LOG: transaction ID wrap limit is 2147484170, limited by database "postgres"

No server settings seem appropriate to remove these...

So, patch enclosed to change LOG -> DEBUG1

Other suggestions welcome...

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

Attachment Content-Type Size
wrap_limit.patch text/x-patch 947 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-09-26 16:06:20 Re: pg_hba.conf: 'trust' vs. 'md5' Issues
Previous Message Zdenek Kotala 2006-09-26 16:03:09 Re: horo(r)logy test fail on solaris (again and solved)

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-09-26 16:24:57 Re: Too many messages from Autovacuum
Previous Message Peter Eisentraut 2006-09-26 12:19:50 Re: Questions about guc units