Re: MultiXactId wraparound and last aggressive vacuum time

2021-04-06 Thread Jehan-Guillaume de Rorthais
On Mon, 5 Apr 2021 17:28:06 -0400 Michael Schanne wrote: > After a closer reading of the documentation, it appears the database should > stop accepting new transactions before a wraparound would ever occur. If > so, then the only possible explanations for this multixactid wraparound > error woul

Re: MultiXactId wraparound and last aggressive vacuum time

2021-04-06 Thread Michael Schanne
After a closer reading of the documentation, it appears the database should stop accepting new transactions before a wraparound would ever occur. If so, then the only possible explanations for this multixactid wraparound error would be data corruption, or a bug in postgresql. The exact version I'

Re: MultiXactId wraparound and last aggressive vacuum time

2021-03-23 Thread Michael Lewis
I don't believe you can determine a date/time that it happened, but querying the age of the table is simple to do and then you can compare that with the freeze age parameters. A periodic manual vacuum freeze may preclude the system ever needing to perform the emergency autovacuum freeze, and as an