"could not reattach to shared memory" on buildfarm member dory

Поиск
Список
Период
Сортировка
От Tom Lane
Тема "could not reattach to shared memory" on buildfarm member dory
Дата
Msg-id 25495.1524517820@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: "could not reattach to shared memory" on buildfarm member dory  (Stephen Frost <sfrost@snowman.net>)
Список pgsql-hackers
So far, dory has failed three times with essentially identical symptoms:

2018-04-23 19:57:10.624 GMT [2240] FATAL:  could not reattach to shared memory (key=0000000000000190,
addr=00000000018E0000):error code 487 
2018-04-23 15:57:10.657 EDT [8836] ERROR:  lost connection to parallel worker
2018-04-23 15:57:10.657 EDT [8836] STATEMENT:  select count(*) from tenk1 group by twenty;
2018-04-23 15:57:10.660 EDT [3820] LOG:  background worker "parallel worker" (PID 2240) exited with exit code 1

Now how can this be?  We've successfully reserved and released the address
range we want to use, so it *should* be free at the instant we try to map.

Another thing that seems curious, though it may just be an artifact of
not having many data points yet, is that these failures all occurred
during pg_upgradecheck.  You'd think the "check" and "install-check"
steps would be equally vulnerable to the failure.

I guess the good news is that we're seeing this in a reasonably
reproducible fashion, so there's some hope of digging down to find
out the actual cause.

            regards, tom lane


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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Should we add GUCs to allow partition pruning to be disabled?