Re: Add Postgres module info - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Add Postgres module info
Date
Msg-id 1085307.1742840674@sss.pgh.pa.us
Whole thread Raw
In response to Re: Add Postgres module info  ("Euler Taveira" <euler@eulerto.com>)
Responses Re: Add Postgres module info
List pgsql-hackers
"Euler Taveira" <euler@eulerto.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



pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: Add Postgres module info
Next
From: Nathan Bossart
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset