re PG 9.6x and found xmin from before relfrozenxid and removal of pg_internal.init file(s)

Поиск
Список
Период
Сортировка
От Reid Thompson
Тема re PG 9.6x and found xmin from before relfrozenxid and removal of pg_internal.init file(s)
Дата
Msg-id 29aee54495d509eb005a8fca1e27ad949fae89da.camel@omnicell.com
обсуждение исходный текст
Ответы Re: re PG 9.6x and found xmin from before relfrozenxid and removal of pg_internal.init file(s)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
We have a planned upgrade that would permanentlty remedy this.

regarding the below errors on our PG 9.6.x instance.

2020-09-28 09:08:15.741 EDT,,,26212,,5f71e03f.6664,1,,2020-09-28 09:08:15 EDT,250/9136136,0,ERROR,XX001,"found xmin
2675436435from before relfrozenxid 321165377",,,,,"automatic vacuum of table ""postgres.pg_catalog.pg_authid""",,,,""
 
2020-09-28 09:08:15.751 EDT,,,26212,,5f71e03f.6664,2,,2020-09-28 09:08:15 EDT,250/9136138,0,ERROR,XX001,"found xmin
2675019557from before relfrozenxid 321165377",,,,,"automatic vacuum of table
""postgres.pg_catalog.pg_auth_members""",,,,""

I know that a db restart will reset the 'counter' (reset the
pg_internal.init files??)  on this issue.  We would rather avoid a
restart if possible. Some research on the internet found a page
suggesting that removal of pg_internal.init file(s) on a running system
would provide the same temporary resolution as a restart???   Is this a
valid temporary work around for this issue?  If it is, is there a
particular pg_internal.init file that needs to be removed, or just
remove all pg_internal.init that can be found?


Thanks,
reid


В списке pgsql-general по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: pg_upgrade Python version issue on openSUSE
Следующее
От: Paul Förster
Дата:
Сообщение: Re: pg_upgrade Python version issue on openSUSE