public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: Josh Innis <[email protected]>
To: [email protected]
Subject: Re: How does Postgres support backwards compatibility
Date: Wed, 09 Feb 2022 16:08:45 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAAZtsUpd_WQe2_OKgcCxWdLL--YaRTnEjYOS=6wrw4pggOZhuQ@mail.gmail.com>
References: <CAAZtsUpd_WQe2_OKgcCxWdLL--YaRTnEjYOS=6wrw4pggOZhuQ@mail.gmail.com>

On Tue, 2022-02-08 at 10:50 -0800, Josh Innis wrote:
> I work on an extension for Postgres. We originally developed the extension for Postgres 11.
> Now we are looking into supporting newer versions of Postgres. We would like our extension
> to be compatible with multiple versions of Postgres. Is there a document that explains how
> the Postgres community handles releases and supports older versions? Any information on how
> Postgres handles this will give us guidance on how to best approach this subject.

PostgreSQL won't break APIs wantonly, but particularly with server internal functions
this happens occasionally.

So it depends a lot on what your extension does.  If it is written in SQL, the odds
are good that it will just continue working.  If it is written in C and you use a lot
of server functions, chances are that you will have to decorate your code with conditional
directives like

#if PG_VERSION_NUM < 130000
...
#else
...
#endif

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com

view thread (4+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: How does Postgres support backwards compatibility
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox