Re: New version numbering practices - Mailing list pgsql-hackers

From Tom Lane
Subject Re: New version numbering practices
Date
Msg-id 31870.1470318347@sss.pgh.pa.us
Whole thread Raw
In response to Re: New version numbering practices  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: New version numbering practices  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
List pgsql-hackers
Craig Ringer <craig@2ndquadrant.com> writes:
> On 4 August 2016 at 12:45, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Craig Ringer <craig@2ndquadrant.com> writes:
>>> Well, this seems like a good time to make server_version_num GUC_REPORT
>>> as well...

>> To what end?  Existing versions of libpq wouldn't know about it, and new
>> versions of libpq couldn't rely on it to get reported by older servers,
>> so it'd still be the path of least resistance to examine server_version.

> Because it's really silly that we don't,

Sorry, but I don't buy that.  I think sending both server_version and
server_version_num would be silly, and we're certainly not going to stop
sending server_version.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: handling unconvertible error messages
Next
From: Tom Lane
Date:
Subject: Re: [RFC] Change the default of update_process_title to off