Re: pg_*_advice: tsv load failure, etc.

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_*_advice: tsv load failure, etc.
Date: 2026-09-10 14:59:19
Message-ID: aqLFxxoTkZkXQrtx@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 10, 2026 at 10:50:14AM -0400, Robert Haas wrote:
> On Thu, Sep 10, 2026 at 9:42 AM Melanie Plageman <melanieplageman(at)gmail(dot)com> wrote:
>> On some level, idea 1 seems like the most appealing because a) it seems
>> quick to do before beta 4 b) it's the easiest to back down from if you
>> find a good way to support this later. If you don't require the schema
>> and later have to do that, you could have advice strings that no longer
>> work.
>
> Fair point. Let me poke at this some more.

I agree with Melanie. Idea 1 seems like the obvious way to go for v19,
especially at this stage of the game. In fact, I think there's a good
argument for keeping it that way long term; I see no benefit to inflicting
more search_path-style issues unless it provides some huge amount of
convenience that we simply cannot pass up.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2026-09-10 15:01:39 Re: Several issues with postgres_fdw stats import
Previous Message Vik Fearing 2026-09-10 14:52:16 Re: Add PRODUCT() aggregate function