pgsql: Be more wary about shm_toc_lookup failure.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Be more wary about shm_toc_lookup failure.
Дата
Msg-id E1ehkoZ-0005uU-48@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Be more wary about shm_toc_lookup failure.

Commit 445dbd82a basically missed the point of commit d46633506,
which was that we shouldn't allow shm_toc_lookup() failure to lead
to a core dump or assertion crash, because the odds of such a
failure should never be considered negligible.  It's correct that
we can't expect the PARALLEL_KEY_ERROR_QUEUE TOC entry to be there
if we have no workers.  But if we have no workers, we're not going
to do anything in this function with the lookup result anyway,
so let's just skip it.  That lets the code use the easy-to-prove-safe
noError=false case, rather than anything requiring effort to review.

Back-patch to v10, like the previous commit.

Discussion: https://postgr.es/m/3647.1517601675@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/957ff087c822c95f63df956e1a91c15614ecb2b4

Modified Files
--------------
src/backend/access/transam/parallel.c | 27 +++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: First-draft release notes for 10.2.
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: pgsql: Fix another instance of unsafe coding for shm_toc_lookup failure