Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)
| От | Tomas Vondra |
|---|---|
| Тема | Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?) |
| Дата | |
| Msg-id | 53bcd88f-2b25-4a7a-949b-64f2960cfc62@vondra.me обсуждение исходный текст |
| Ответ на | Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?) (Peter Geoghegan <pg@bowt.ie>) |
| Ответы |
Re: suspicious lockup on widowbird in AdvanceXLInsertBuffer (could it be due to 6a2275b8953?)
|
| Список | pgsql-hackers |
On 2/26/25 23:13, Peter Geoghegan wrote: > On Wed, Feb 26, 2025 at 5:09 PM Tomas Vondra <tomas@vondra.me> wrote: >> So, it's stuck in AdvanceXLInsertBuffer ... interesting. Another >> interesting fact is it's testing 75dfde13639, which is just a couple >> commits after 6a2275b895: > >> which reworked AdvanceXLInsertBuffer() quite a bit, it seems. OTOH the >> last (successful) run on widorbird was on eaf502747b, which already >> includes 6a2275b895, so maybe it's unrelated. > > Are you aware that Alexander reverted this only a day later, in commit 3fb58625? > Oh, I forgot about that. I guess if the theory is the commit might be causing this, and it's been already reverted, I should just restart the instance, so that it tests with the revert. regards -- Tomas Vondra
В списке pgsql-hackers по дате отправления: