Re: Extended Statistics set/restore/clear functions.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, pgsql-hackers(at)lists(dot)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: Extended Statistics set/restore/clear functions.
Date: 2025-11-25 10:06:09
Message-ID: aSV_kS5_pL4DYw1J@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 25, 2025 at 04:59:28PM +0800, Chao Li wrote:
> I don’t see any of my comments are addressed in v18.

Sorry about that, I thought that v17 was addressing these. I have
reviewed your latest email posted here:
https://www.postgresql.org/message-id/2C8A20C7-4E08-41F4-B30E-AD9F8B007AE5@gmail.com

And well, this presents a bunch of issues I have already fixed (break
after return, one error message incorrect, some descriptions). The
comments on top of the functions are actually true as they stand (aka
ndistinct_array_end() fails if we don't have an array). There is no
need to reset state vars upon a JSON_SEM_ACTION_FAILED AFAIK.
Finally, the consts are non-appealing for me for functions that are
internally used in these files. And forgot one:
valid_subsequent_attnum()'s duplication is actually adapted IMO, the
argument lists could have different assumptions depending on the type
of extended stats we are dealing with. I did not check the comments
for 0003~0005. Perhaps you are right that these need adjustments.

Thanks,
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2025-11-25 10:07:24 Re: BUG #19095: Test if function exit() is used fail when linked static
Previous Message Dean Rasheed 2025-11-25 10:04:36 Re: ON CONFLICT DO SELECT (take 3)