Re: proposal - get_extension_version function

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jacob Champion <jchampion(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: proposal - get_extension_version function
Date: 2023-03-09 04:35:20
Message-ID: CAFj8pRCYHqTdBxmA3pRJ5Y-nUY6zzAk_T1iqS_G_iGqxP5T66A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

st 8. 3. 2023 v 23:43 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:

> Jacob Champion <jchampion(at)timescale(dot)com> writes:
> > What I'm trying to pin down is the project's position on the reverse
> > -- binary version X and SQL version X+1 -- because that seems
> > generally unmaintainable, and I don't understand why an author would
> > pay that tax if they could just avoid it by bailing out entirely. (If
> > an author wants to allow that, great, but does everyone have to?)
>
> Hard to say. Our experience with the standard contrib modules is that
> it really isn't much additional trouble; but perhaps more-complex modules
> would have more interdependencies between functions. In any case,
> I fail to see the need for basing things on a catalog lookup rather
> than embedding API version numbers in relevant C symbols.
>

How can you check it? There is not any callback now.

Regards

Pavel

>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-03-09 04:49:02 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Previous Message vignesh C 2023-03-09 04:23:40 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher