Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Add new variable "server_version_num", which is almost the same

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Add new variable "server_version_num", which is almost the same
Date: 2006-09-02 14:30:06
Message-ID: 2337.1157207406@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
momjian(at)postgresql(dot)org (Bruce Momjian) writes:
> Add new variable "server_version_num", which is almost the same as
> "server_version" but uses the handy PG_VERSION_NUM which allows apps to
> do things like if ($version >= 80200) without having to parse apart the
> value of server_version themselves.

I thought this was rejected as being utterly useless.  Or is this commit
somehow going to retroactively affect existing old servers?

A non-useless version of this would be client-side code ... except it's
already there, in libpq at least.

Please revert.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-09-02 14:46:07
Subject: Re: [COMMITTERS] pgsql: Suppress some NOTICE
Previous:From: Tom LaneDate: 2006-09-02 14:27:14
Subject: Re: [HACKERS] Resurrecting per-page cleaner for

pgsql-committers by date

Next:From: Tom LaneDate: 2006-09-02 14:46:07
Subject: Re: [COMMITTERS] pgsql: Suppress some NOTICE
Previous:From: Tom LaneDate: 2006-09-02 14:25:15
Subject: Re: [COMMITTERS] pgsql: Allow PL/python to return composite types and result sets Sven

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group