Avoid Wraparound Failures - Mailing list pgsql-admin

From Loles
Subject Avoid Wraparound Failures
Date
Msg-id CA+FWGK6HmRx8=-2wZkw-9a6a36f6iEGgAH=bN1rNicbFgzas5A@mail.gmail.com
Whole thread Raw
Responses Re: Avoid Wraparound Failures  (Ron <ronljohnsonjr@gmail.com>)
Re: Avoid Wraparound Failures  (Laurenz Albe <laurenz.albe@cybertec.at>)
Re: Avoid Wraparound Failures  (Vijaykumar Jain <vijaykumarjain.github@gmail.com>)
List pgsql-admin
Hi!

Suppose the databases on my instance are near to have a wraparound failure.

(I think so, from what I see, but in the PostgreSQL log I haven't seen any warning about It yet).

What do I have to do?

vacuum freeze;

better than,

vacuum analyze;

Or both?

If the autovacuum_freeze configuration parameters have defaults values, should I modify any first?

More I read of this topic, more confused I am.

Please, I need simple and wise advice :)

Thanks!

pgsql-admin by date:

Previous
From: Dirk Krautschick
Date:
Subject: Vacuum behaviour for replicated nodes with pglogical (postgres 10)
Next
From: Ron
Date:
Subject: Re: Avoid Wraparound Failures