pgsql: Fix comment in LockReleaseAll() on when locallock->nLock can be

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix comment in LockReleaseAll() on when locallock->nLock can be
Date: 2024-11-04 13:48:19
Message-ID: E1t7xRK-0008Wm-Oa@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2024-11-04 14:02:08 Re: pgsql: Implement pg_wal_replay_wait() stored procedure
Previous Message Heikki Linnakangas 2024-11-04 12:25:37 pgsql: Make PG_TEST_EXTRA env var override the "meson setup" option