| From: | Xuneng Zhou <xunengzhou(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Update EnableTimeoutParams timeout type comment |
| Date: | 2026-07-01 01:43:40 |
| Message-ID: | CABPTF7XuFqwOcBJ1x0rTKvEvvQ+zfZVidmjTybJPmu9_zTL6Ug@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Hackers,
While reading the timeout code, I noticed that the comment for
EnableTimeoutParams timeout type is kinda stale. Currently, we support
three types of timeout TMPARAM_AFTER/AT/EVERY, but the comment only
mentions the first two. It may not cause confusion, since the two
structs are adjacent, but it might still be worth making this clearer.
Attached a patch to update it.
--
Regards,
Xuneng Zhou
HighGo Software Co., Ltd.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Update-EnableTimeoutParams-timeout-type-comment.patch | application/octet-stream | 985 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guoqing Yang | 2026-07-01 01:44:53 | Fix Grammar in Buffer Lock Wait Message |
| Previous Message | Michael Paquier | 2026-07-01 01:35:33 | Re: Add pg_stat_kind_info system view |