Re: Can we let extensions change their dumped catalog schemas?

From: Jacob Champion <jchampion(at)timescale(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Can we let extensions change their dumped catalog schemas?
Date: 2023-01-12 19:04:49
Message-ID: CAAWbhmjZ8Arz9siYijAktq-v89JYmC2xqgodF9M_pz7zsHTpFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 11, 2023 at 1:03 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jacob Champion <jchampion(at)timescale(dot)com> writes:
> > Right, I think it would have to be opt-in. Say, a new control file
> > option dump_version or some such.
>
> That would require all the installed extensions to cope with this
> the same way, which does not seem like a great assumption.

How so? Most installed extensions would not opt into a version dump,
I'd imagine.

Or do you mean that the version dump would apply retroactively to
older versions of the extension, even if it wasn't needed in the past?

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message mahendrakar s 2023-01-12 19:08:35 Re: [PoC] Federated Authn/z with OAUTHBEARER
Previous Message Nathan Bossart 2023-01-12 18:44:33 Re: PL/Python: Fix return in the middle of PG_TRY() block.