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

• pgsql: Add new variable "server_version_num", which is almost the same at 2006-09-02 13:12:50 from Bruce Momjian

Responses

• Re: [COMMITTERS] pgsql: Add new variable at 2006-09-02 14:48:51 from Bruce Momjian
• Re: [COMMITTERS] pgsql: Add new variable "server_version_num", which is almost the same at 2006-09-02 16:39:16 from Tom Lane

pgsql-hackers by date

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

pgsql-committers by date

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