pgsql: Teach libpq to decode server version correctly from future serve - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Teach libpq to decode server version correctly from future serve
Date
Msg-id E1bVo4q-0003ra-2U@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Teach libpq to decode server version correctly from future servers.

Beginning with the next development cycle, PG servers will report two-part
not three-part version numbers.  Fix libpq so that it will compute the
correct numeric representation of such server versions for reporting by
PQserverVersion().  It's desirable to get this into the field and
back-patched ASAP, so that older clients are more likely to understand the
new server version numbering by the time any such servers are in the wild.

(The results with an old client would probably not be catastrophic anyway
for a released server; for example "10.1" would be interpreted as 100100
which would be wrong in detail but would not likely cause an old client to
misbehave badly.  But "10devel" or "10beta1" would result in sversion==0
which at best would result in disabling all use of modern features.)

Extracted from a patch by Peter Eisentraut; comments added by me

Patch: <802ec140-635d-ad86-5fdf-d3af0e260c22@2ndquadrant.com>

Branch
------
REL9_5_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/cae0d4f9ba5f34fe27a5806f23df6fa6e2785e35

Modified Files
--------------
src/interfaces/libpq/fe-exec.c | 27 ++++++++++++++++++++++-----
1 file changed, 22 insertions(+), 5 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Teach libpq to decode server version correctly from future serve
Next
From: Tom Lane
Date:
Subject: pgsql: Teach libpq to decode server version correctly from future serve