Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Tue, 26 Sep 2006 17:04:26 +0100
- Message-id: <1159286666.2696.27.camel@holly> <text/plain>
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:
wrap_limit.patch
Description: Text Data
- Follow-Ups:
- Re: Too many messages from Autovacuum
- From: Alvaro Herrera
- Re: Too many messages from Autovacuum
- From: Tom Lane
- Re: Too many messages from Autovacuum
- Prev by Date: Re: [HACKERS] large object regression tests
- Next by Date: Re: Too many messages from Autovacuum
- Previous by thread: guc units cleanup
- Next by thread: Re: Too many messages from Autovacuum
- Indexes: