Re: amcheck packages

On Mon, Oct 2, 2017 at 11:29 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> They could be co-installable, by changing symbol names. There is going
> to be a contrib amcheck 1.1 before too long, so if I'm not going to
> change the name of the extension, I should at least make sure that the
> version numbers stay in a non-overlapping range, to make sure that
> there is never confusion during upgrade.

It turns out that Postgres is totally naive about external modules
that happen to have the same name as contrib modules. I think that I
have no choice but to create a new extension name -- "amcheck-next",
say. This can have extension version numbers that begin at 1.0.

Without this, the control file of the external version simply
overwrites the contrib version as part of "make install". That's
clearly not okay.

--
Peter Geoghegan