Re: Row pattern recognition

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: assam258(at)gmail(dot)com
Cc: jian(dot)universality(at)gmail(dot)com, zsolt(dot)parragi(at)percona(dot)com, sjjang112233(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, peter(at)eisentraut(dot)org, li(dot)evan(dot)chao(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Row pattern recognition
Date: 2026-09-08 07:18:26
Message-ID: 20260908.161826.431346548851592287.ishii@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Henson,

> Hi Tatsuo,
>
>> So my plan for v52 is, using PG_USED_FOR_ASSERTS_ONLY
>> for "pattern" as below. Does this work for you?
>
> Yes, I think that works.
>
> Another way is to have the Assert read winstate->rpPattern in place
> of the local:
>
> Assert(elem->next >= 0 &&
> elem->next < winstate->rpPattern->numElements);
>
> Either is fine. 2013 in the increment removes the local, so the two
> end up at the same place.

Thanks for confirmation. I will go for PG_USED_FOR_ASSERTS_ONLY.

Regards,
--
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 Álvaro Herrera 2026-09-08 07:25:25 Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Previous Message Antonin Houska 2026-09-08 07:17:31 Re: REPACK (CONCURRENTLY) backend waits indefinitely when decoding worker fails to start