| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Euler Taveira" <euler(at)eulerto(dot)com> |
| Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Andrei Lepikhov" <lepihov(at)gmail(dot)com>, "Michael Paquier" <michael(at)paquier(dot)xyz>, "Alexander Korotkov" <aekorotkov(at)gmail(dot)com>, "Yurii Rashkovskii" <yrashk(at)omnigres(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add Postgres module info |
| Date: | 2025-03-24 18:24:34 |
| Message-ID: | 1085307.1742840674@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Euler Taveira" <euler(at)eulerto(dot)com> writes:
> I think those modules without control file, it is natural to use PG_VERSION.
> However, I'm concerned that users can confuse the version if we provide
> PG_VERSION as version and the extension catalog says something different.
Maybe, but the values will be sufficiently different that I don't
think the confusion will last long. Anyway I don't want the version
in an extension's module to mean something totally different than
the version in a non-extension module. I could possibly get behind
setting version = PG_VERSION and having another field "ext_version"
or such that shows the expected current extension version if the
module belongs to an extension. I'm not really convinced it's worth
the trouble, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-03-24 18:45:27 | Re: vacuum_truncate configuration parameter and isset_offset |
| Previous Message | Euler Taveira | 2025-03-24 18:14:23 | Re: Add Postgres module info |