Re: Update EnableTimeoutParams timeout type comment

From: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Update EnableTimeoutParams timeout type comment
Date: 2026-07-01 01:49:55
Message-ID: CABPTF7WtRLaVKq9WUh=2adBSFGfyAmBdJCFc-PxYDRzndDMUqQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 1, 2026 at 9:43 AM Xuneng Zhou <xunengzhou(at)gmail(dot)com> wrote:
>
> 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.

Opus, it should be "the struct and the enum", not two structs.

--
Regards,
Xuneng Zhou
HighGo Software Co., Ltd.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message wenhui qiu 2026-07-01 01:53:36 Re: WAL compression setting after PostgreSQL LZ4 default change
Previous Message Tender Wang 2026-07-01 01:49:31 Re: Fix HAVING-to-WHERE pushdown with mismatched operator families