Setting PG-version without recompiling

At 2014-07-03 11:02:34 +0200, andreas@visena.com wrote:

Is it possible to set this somewhere without
recompiling PG?

I'm afraid not.

-- Abhijit

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

På torsdag 03. juli 2014 kl. 11:13:44, skrev Abhijit Menon-Sen <
ams@2ndQuadrant.com <mailto:ams@2ndQuadrant.com>>: At 2014-07-03 11:02:34
+0200, andreas@visena.com wrote:

Is it possible to set this somewhere without
recompiling PG?

I'm afraid not.   Ok   -- Andreas Jospeh Krogh CTO / Partner - Visena AS
Mobile: +47 909 56 963 andreas@visena.com <mailto:andreas@visena.com>
www.visena.com <https://www.visena.com&gt; <https://www.visena.com&gt;  

Andreas Joseph Krogh <andreas@visena.com> writes:

Hi.   I'm up for testing 9.4 but my JDBC-driver fails to connect due to PG's
minor-version string: "4beta1". Is it possible to set this somewhere without
recompiling PG?

No, and even if you could, that would be the wrong approach. The right
approach is to fix the JDBC driver to not complain about such version
strings. I'm a bit surprised they haven't done so long since, considering
how long PG beta versions have been tagged like that. For that matter,
they really ought not complain about strings like "9.5devel" or
"9.5alpha2" either.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

På torsdag 03. juli 2014 kl. 16:16:01, skrev Tom Lane <tgl@sss.pgh.pa.us
<mailto:tgl@sss.pgh.pa.us>>: Andreas Joseph Krogh <andreas@visena.com> writes:

Hi. �� I'm up for testing 9.4 but my JDBC-driver fails to connect due to

PG's

minor-version string: "4beta1". Is it possible to set this somewhere without
recompiling PG?

No, and even if you could, that would be the wrong approach.  The right
approach is to fix the JDBC driver to not complain about such version
strings.  I'm a bit surprised they haven't done so long since, considering
how long PG beta versions have been tagged like that.  For that matter,
they really ought not complain about strings like "9.5devel" or
"9.5alpha2" either.

regards, tom lane   I'm using the pgjdbc-ng driver, I'm sure the "official"
driver handles this. The driver will be fixed (the issue has a pull-request), I
just wondered if there was a magic know I could use until the PR is merged.   --
Andreas Jospeh Krogh CTO / Partner - Visena AS Mobile: +47 909 56 963
andreas@visena.com <mailto:andreas@visena.com> www.visena.com
<https://www.visena.com&gt; <https://www.visena.com&gt;  

On 07/03/2014 10:16 PM, Tom Lane wrote:

Andreas Joseph Krogh <andreas@visena.com> writes:

Hi. � I'm up for testing 9.4 but my JDBC-driver fails to connect due to PG's
minor-version string: "4beta1". Is it possible to set this somewhere without
recompiling PG?

No, and even if you could, that would be the wrong approach. The right
approach is to fix the JDBC driver to not complain about such version
strings. I'm a bit surprised they haven't done so long since, considering
how long PG beta versions have been tagged like that. For that matter,
they really ought not complain about strings like "9.5devel" or
"9.5alpha2" either.

Yeah, that's horrible. We should be using server_version_num .

It should be a quick enough fix, I'll take a look.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers