Re: proposal - get_extension_version function

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Jacob Champion <jchampion(at)timescale(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: proposal - get_extension_version function
Date: 2023-03-08 19:10:37
Message-ID: CAFj8pRCErENz5wV9z6V-ttu5HbMPoS7juc7bN8i+=MDo6qRZJA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

st 8. 3. 2023 v 20:04 odesílatel Jacob Champion <jchampion(at)timescale(dot)com>
napsal:

> On Wed, Mar 8, 2023 at 10:49 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > This is a bad idea. How will you do extension upgrades, if the new .so
> > won't run till you apply the extension upgrade script but the old .so
> > malfunctions as soon as you do?
>
> Which upgrade paths allow you to have an old .so with a new version
> number? I didn't realize that was an issue.
>

installation from rpm or deb packages

> --Jacob
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-03-08 19:17:56 Re: proposal - get_extension_version function
Previous Message Jacob Champion 2023-03-08 19:04:28 Re: proposal - get_extension_version function