Re: collect_corrupt_items_vacuum.patch
От | Alexander Korotkov |
---|---|
Тема | Re: collect_corrupt_items_vacuum.patch |
Дата | |
Msg-id | CAPpHfdscrsKdw12Xi8zgkmUCYuL3RCXAJF-a_pK0-QZ=1hQq2w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: collect_corrupt_items_vacuum.patch (Heikki Linnakangas <hlinnaka@iki.fi>) |
Ответы |
Re: collect_corrupt_items_vacuum.patch
|
Список | pgsql-hackers |
On Tue, Aug 13, 2024 at 9:39 PM Heikki Linnakangas <hlinnaka@iki.fi> wrote: > > This causes an assertion failure when executed in a hot standby server: > > select * from pg_check_visible('pg_database'); > > TRAP: failed Assert("!RecoveryInProgress()"), File: > "../src/backend/storage/ipc/procarray.c", Line: 2710, PID: 1142572 > > GetStrictOldestNonRemovableTransactionId does this: > > > if (rel == NULL || rel->rd_rel->relisshared || RecoveryInProgress()) > > { > > /* Shared relation: take into account all running xids */ > > runningTransactions = GetRunningTransactionData(); > > LWLockRelease(ProcArrayLock); > > LWLockRelease(XidGenLock); > > return runningTransactions->oldestRunningXid; > > } > > And GetRunningTransactionData() has this: > > > Assert(!RecoveryInProgress()); > > So it's easy to see that you will hit that assertion. Oh, thank you! I'll fix this and add a test for recovery! ------ Regards, Alexander Korotkov Supabase
В списке pgsql-hackers по дате отправления: