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
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'
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
Hi,
My application is getting the following exception:
InternalError: (psycopg2.InternalError) MultiXactId 808263738 has not been
created yet -- apparent wraparound
I read over
https://www.postgresql.org/docs/9.6/routine-vacuuming.html#VACUUM-FOR-MULTIXACT-WRAPAROUND
and I suspect the issue was
