Fwd: [HACKERS] Syncing sql extension versions with shared library versions

Mat Arye <mat@timescaledb.com> writes:
> I tried looking in the contrib modules and didn't find many with lots of
> planner hook usage.

I'm not really sure why planner hooks would have anything to do with your
exposed SQL API?

You will need to have separate builds of your extension for each PG
release branch you work with; we force that through PG_MODULE_MAGIC
whether you like it or not.  But that doesn't translate to needing
different names for the library .so files.  Generally people either
mantain separate source code per-branch (just as the core code does)
or put in a lot of #ifs testing CATALOG_VERSION_NO to see which
generation of PG they're compiling against.