Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: dgrowleyml(at)gmail(dot)com, li(dot)evan(dot)chao(at)gmail(dot)com
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)lists(dot)postgresql(dot)org, pramsey(at)cleverelephant(dot)ca, ojford(at)gmail(dot)com, peter(at)eisentraut(dot)org, krasiyan(at)gmail(dot)com, vik(at)postgresfriends(dot)org, andrew(at)tao11(dot)riddles(dot)org(dot)uk, david(at)fetter(dot)org
Subject: Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options
Date: 2025-10-23 02:06:59
Message-ID: 20251023.110659.292357580714448419.ishii@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> On Mon, 20 Oct 2025 at 16:59, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>>>
>>> > A very trivial commit:
>>> >
>>> > ```
>>> > + else
>>> > +
>>> > + /*
>>> > + * For other cases we have no idea what position of row callers would
>>> > + * fetch next time. Also for relpos < 0 case (we go backward), we
>>> > + * cannot set mark either. For those cases we always set mark at 0.
>>> > + */
>>> > + mark_pos = 0;
>>> > ```
>>> >
>>> > The empty line after “else” is not needed.
>>>
>>> That was added by pgindent.
>>
>> If it's written down somewhere, I can't find it, but the rule we
>> normally follow here is; don't use braces if the code block has a
>> single statement without any comments that appear on a separate line.
>> Otherwise, use braces.
>
> Oh ok, I didn't know that.
>
>> Since your comments are not on the same line as the statement, it
>> should have braces. I imagine that's why pgindent is "acting weird".
>
> Attached is a trivial patch to follow the rule.

Patch pushed. Thanks.
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jiaoshuntian 2025-10-23 02:31:01 Identifying Schema-Qualified Sequence References in Column Defaults
Previous Message Tom Lane 2025-10-23 01:49:19 Memory leak due to thinko in PL/Python error handling