From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sebastien FLAESCH <sf(at)4js(dot)com> |
Cc: | hlinnaka(at)iki(dot)fi, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Details about libpq cross-version compatibility |
Date: | 2012-09-13 22:25:07 |
Message-ID: | 23464.1347575107@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Sebastien FLAESCH <sf(at)4js(dot)com> writes:
> If a future major version (for ex 9.3) implements a new strategic feature
> that makes libpq headers incompatible with prior versions, what shall we
> do with our convention? Shall we ship 9.x (where 0<=x<=2) drivers and 9.3+
> drivers? What if a next major version implements again another feature
> that makes headers incompatible again?
We've never done that AFAIR. When and if it happens, that would be the
time to deal with it.
> I think I am asking for is an official statement that clearly says that
> libpq headers are only compatible for a given set of minor versions, like
> (8.4.1, 8.4.2, 8.4.3, ...) or (9.2.1, 9.2.2, ...)
> I believe also that the libpq library should automatically check for
> compatiblity, based on PG_MAJORVERSION definition in pg_config.h ...
It seems highly undesirable to me that we should intentionally break
cross-version compatibility, which is what you seem to be proposing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sebastien FLAESCH | 2012-09-14 09:43:43 | Re: Details about libpq cross-version compatibility |
Previous Message | Tom Lane | 2012-09-13 17:33:19 | Re: Planner selects different execution plans depending on limit |