| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jacob Champion <jchampion(at)timescale(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: proposal - get_extension_version function |
| Date: | 2023-03-08 21:47:22 |
| Message-ID: | 251200.1678312042@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jacob Champion <jchampion(at)timescale(dot)com> writes:
> On Wed, Mar 8, 2023 at 11:11 AM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> installation from rpm or deb packages
> Right, but I thought the safe order for a downgrade was to issue the
> SQL downgrade first (thus putting the system back into the
> post-upgrade state), and only then replacing the packages with prior
> versions.
Pavel's proposed check would break that too. There's going to be some
interval where the SQL definitions are not in sync with the .so version,
so you really want the .so to support at least two versions' worth of
SQL objects.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2023-03-08 22:07:22 | Re: RFC: logical publication via inheritance root? |
| Previous Message | Andrew Dunstan | 2023-03-08 21:40:05 | Re: SQL/JSON revisited |