Re: MultiXactId Error in Autovacuum

Поиск
Список
Период
Сортировка
От Karl Hafner
Тема Re: MultiXactId Error in Autovacuum
Дата
Msg-id CA+MJ4cTqPEn1f4irCTM4d71E0YrBZTKfcmnJ6y9DPVSHSkXCDQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: MultiXactId Error in Autovacuum  (Albe Laurenz <laurenz.albe@wien.gv.at>)
Ответы Re: MultiXactId Error in Autovacuum  (Albe Laurenz <laurenz.albe@wien.gv.at>)
Список pgsql-admin
Hi Laurenz, 

thank you for looking into my issue. 


Do you know if you experienced transaction ID wraparound as the
message suggests?

I am not aware of a wraparound in the past. I am quite sure no. 


Are there any other questionable messages in the log?

The log shows nothing special except this error that is always associated with the same MultiXactId 2683601542.
 

What do you get for the following queries:

SELECT txid_current();

txid_current 
--------------
1673482898
 

SELECT datname, datfrozenxid FROM pg_database;


SELECT datname, datfrozenxid FROM pg_database;

datname  | datfrozenxid 
-----------+--------------
postgres  |   1497699916
template0 |   1497699916
MYDB      |   1335927866
template1 |   1497699916


 

SELECT current_setting('autovacuum_freeze_max_age'),
       current_setting('vacuum_freeze_min_age'),
       current_setting('vacuum_freeze_table_age');


current_setting | current_setting | current_setting 
-----------------+-----------------+-----------------
200000000       | 50000000        | 150000000


Thank you!
Best regards, 
Karl

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

Предыдущее
От: Gary Stainburn
Дата:
Сообщение: Postgresql not accessible, recovering
Следующее
От: Luca Ferrari
Дата:
Сообщение: Re: How to install pgagent on linux?