| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | Guoqing Yang <yanggq1988(at)126(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Fix Grammar in Buffer Lock Wait Message |
| Date: | 2026-07-01 02:02:34 |
| Message-ID: | E13B3352-7CA0-46F4-A583-FB9213083AEF@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Jul 1, 2026, at 09:44, Guoqing Yang <yanggq1988(at)126(dot)com> wrote:
>
> Fix grammar in buffer lock wait message
> Correct the wait message from "Waiting to acquire a exclusive lock on a buffer"
> to "Waiting to acquire an exclusive lock on a buffer".
> The word "exclusive" starts with a vowel sound, so the indefinite article
> should be "an" instead of "a".
> Regards,
> Guoqing Yang
>
Nice catch.
The typo is in wait_event_names.txt, so it actually affects the docs. See the attached doc screenshot.
```
BufferCleanup Waiting to acquire **an exclusive** pin on a buffer. Buffer pin waits can be
BufferExclusive Waiting to acquire **a exclusive** lock on a buffer.
```
The row right above it uses “an exclusive”, while the next row uses “a exclusive”.
This seems to be an oversight from 6c5c393b7, so I think it should be back-patched to 19.
Best regards,*
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| Attachment | Content-Type | Size |
|---|---|---|
| wait_event_name.png | image/png | 86.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2026-07-01 02:04:35 | Re: Fix HAVING-to-WHERE pushdown with mismatched operator families |
| Previous Message | wenhui qiu | 2026-07-01 01:53:36 | Re: WAL compression setting after PostgreSQL LZ4 default change |