Re: Avoid repeated scans of the output buffer in oidvectortypes()

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoid repeated scans of the output buffer in oidvectortypes()
Date: 2026-10-16 02:08:48
Message-ID: BEECB75B-038A-405C-A5DF-EF6B9080DBBB@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Oct 15, 2026, at 21:52, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>
> On 15/10/2026 15:49, David Rowley wrote:
>> On Fri, 16 Oct 2026 at 01:16, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>>> I agree that using the usual API outweigh these minor considerations. I've updated the patch to use StringInfo in v2.
>> v2 looks fine to me.
>
> Committed, thanks.
>
> - Heikki
>

Thanks a lot for pushing.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-10-16 02:34:44 Re: Avoid repeated scans of the output buffer in oidvectortypes()
Previous Message Manu 2026-10-16 01:56:17 Re: ATTACH PARTITION cost grows linearly with pg_constraint size (seqscan in CloneFkReferenced), much worse since not-null constraints are in pg_constraint (PG 18)