Re: Add expressions to pg_restore_extended_stats()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Tender Wang <tndrwang(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(at)vondra(dot)me>
Subject: Re: Add expressions to pg_restore_extended_stats()
Date: 2026-02-04 06:23:59
Message-ID: aYLl__4eJ6LObs9i@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 04, 2026 at 01:13:05AM -0500, Corey Huinker wrote:
>> Hmm. I am not sure, that depends. How much additional information
>> would these extra parameter bring to the errors generated in
>> statatt_build_stavalues().
>
> Just the index of which expression and the name of the key that fed in the
> offending value string.

Okay. It really sounds to me like an ErrorContextCallback would help
you here. I don't see a need to complicate statatt_build_stavalues(),
but my intuition can also be wrong.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-02-04 06:26:25 Re: Warn when creating or enabling a subscription with max_logical_replication_workers = 0
Previous Message Michael Paquier 2026-02-04 06:21:29 Re: Add LIMIT option to COPY FROM