Too many messages from Autovacuum

Started by Simon Riggsover 19 years ago3 messages
#1Simon Riggs
simon@2ndquadrant.com
1 attachment(s)

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

Attachments:

wrap_limit.patchtext/x-patch; charset=UTF-8; name=wrap_limit.patchDownload
Index: src/backend/access/transam/varsup.c
===================================================================
RCS file: /projects/cvsroot/pgsql/src/backend/access/transam/varsup.c,v
retrieving revision 1.73
diff -c -r1.73 varsup.c
*** src/backend/access/transam/varsup.c	3 Sep 2006 15:59:38 -0000	1.73
--- src/backend/access/transam/varsup.c	26 Sep 2006 15:27:49 -0000
***************
*** 239,245 ****
  	LWLockRelease(XidGenLock);
  
  	/* Log the info */
! 	ereport(LOG,
  	   (errmsg("transaction ID wrap limit is %u, limited by database \"%s\"",
  			   xidWrapLimit, NameStr(*oldest_datname))));
  	/* Give an immediate warning if past the wrap warn point */
--- 239,245 ----
  	LWLockRelease(XidGenLock);
  
  	/* Log the info */
! 	ereport(DEBUG1,
  	   (errmsg("transaction ID wrap limit is %u, limited by database \"%s\"",
  			   xidWrapLimit, NameStr(*oldest_datname))));
  	/* Give an immediate warning if past the wrap warn point */
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Simon Riggs (#1)
Re: Too many messages from Autovacuum

Simon Riggs <simon@2ndquadrant.com> writes:

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"

Seems reasonable --- we put that in at LOG level for purposes of testing
the 8.1 XID wraparound prevention logic, but by now I think we can trust
that code a bit more.

regards, tom lane

#3Alvaro Herrera
alvherre@commandprompt.com
In reply to: Simon Riggs (#1)
Re: Too many messages from Autovacuum

Simon Riggs wrote:

No server settings seem appropriate to remove these...

So, patch enclosed to change LOG -> DEBUG1

Applied, thanks.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support