| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Mat Arye <mat(at)timescaledb(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Syncing sql extension versions with shared library versions |
| Date: | 2017-07-22 14:50:16 |
| Message-ID: | CA+TgmobSYLen8NVD4U5qbSeeHjAoSBzxOs-wSNn43tXHzBg4JA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 21, 2017 at 4:17 PM, Mat Arye <mat(at)timescaledb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-07-22 15:00:54 | Re: Syncing sql extension versions with shared library versions |
| Previous Message | Michael Paquier | 2017-07-22 05:50:29 | Re: Error while copying a large file in pg_rewind |