Re: Get rid of WALBufMappingLock

From: Victor Yegorov <vyegorov(at)gmail(dot)com>
To: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Get rid of WALBufMappingLock
Date: 2025-02-17 08:46:57
Message-ID: CAGnEbogrHOrXw8vaR3QP4hkEABF=L4VZaaViE3f5Ci+gP2cTeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hey.

I find “Get rid of WALBufMappingLock" commit message misleading, 'cos Lock
it's being replaced by CV, actually.

Should the subject be changed to “Replace WALBufMappingLock with
ConditionVariable” instead?

--
Victor Yegorov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2025-02-17 09:02:51 Re: Commitfest app release on Feb 17 with many improvements
Previous Message wenhui qiu 2025-02-17 08:46:13 Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations