Обсуждение: Too many messages from Autovacuum

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

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

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