From: Heikki Linnakangas <heikki.linnakangas@iki.fi>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix comment in LockReleaseAll() on when locallock->nLock can be
Date: Mon, 04 Nov 2024 13:48:19 +0000
Message-ID: <E1t7xRK-0008Wm-Oa@gemulon.postgresql.org> (raw)
Fix comment in LockReleaseAll() on when locallock->nLock can be zero
We reach this case also e.g. when a deadlock is detected, not only
when we run out of memory.
Reviewed-by: Maxim Orlov
Discussion: https://www.postgresql.org/message-id/7c2090cd-a72a-4e34-afaa-6dd2ef31440e@iki.fi
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/1fe0466cf2cbb909b6553061620b6a6779319406
Modified Files
--------------
src/backend/storage/lmgr/lock.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: heikki.linnakangas@iki.fi, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix comment in LockReleaseAll() on when locallock->nLock can be
In-Reply-To: <E1t7xRK-0008Wm-Oa@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox