Re: buildfarm: could not read block 3 in file "base/16384/2662": readonly 0 of 8192 bytes

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: buildfarm: could not read block 3 in file "base/16384/2662": readonly 0 of 8192 bytes
Дата
Msg-id CAH2-Wz=BBiSAB2srBtbW1eEGgMdZR-623Jd6kTKz-Lo+ZzQijA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: buildfarm: could not read block 3 in file "base/16384/2662": readonly 0 of 8192 bytes
Список pgsql-hackers
On Wed, Aug 8, 2018 at 10:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Typically not, but I don't think that we can rule it out right away.
>
> Hmmm ... maybe we should temporarily stick in an elog(LOG) showing whether
> a parallel build happened or not, so that we can check the buildfarm logs
> next time we see that failure?

I can do that tomorrow. Of course, it might be easier to just push the
pending fix for the mapped relation bug, and see if that makes the
issue go away. That would take longer, but it's also the only thing
that's likely to be definitive anyway.

If you want to go ahead with it yourself, I suggest modifying the
DEBUG1 elog()s within index_build() to be LOG elevel.

-- 
Peter Geoghegan


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Temporary tables prevent autovacuum, leading to XID wraparound