Re: [HACKERS] Syncing sql extension versions with shared library versions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Syncing sql extension versions with shared library versions
Date
Msg-id CA+TgmobSYLen8NVD4U5qbSeeHjAoSBzxOs-wSNn43tXHzBg4JA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Syncing sql extension versions with shared library versions  (Mat Arye <mat@timescaledb.com>)
Responses Re: [HACKERS] Syncing sql extension versions with shared library versions
Re: [HACKERS] Syncing sql extension versions with shared library versions
List pgsql-hackers
On Fri, Jul 21, 2017 at 4:17 PM, Mat Arye <mat@timescaledb.com> wrote:
> (I
> want to avoid having to keep backwards-compatibility for all functions in
> future shared-libraries).

Are you sure that's a good idea?  It seems like swimming upstream
against the design.  I mean, instead of creating a dispatcher library
that loads either v1 or v2, maybe you could just put it all in one
library, add a "v1" or "v2" suffix to the actual function names where
appropriate, and then set up the SQL definitions to call the correct
one.  I mean, it's the same thing, but with less chance of the dynamic
loader ruining your day.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Error while copying a large file in pg_rewind
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Syncing sql extension versions with shared library versions