Hmm, there must be _some_ parsing going on, because
select current_setting('server_version')
returns "10.2 (Ubuntu 10.2-1.pgdg16.04+1)" on the Ubuntu installation, so I wonder how the 10.2.2 is created from that
bythe JDBC driver.
It is not really important, I am just wondering...
Regards
Thomas
Jorge Solórzano schrieb am 19.02.2018 um 18:04:
> The DatabaseMetaData.getDatabaseProductVersion() returns the exact
> string of ParameterStatus "server_version", and this version can be
> different from ditro to distro, in my Ubuntu the "server_version"
> returns: "10.2 (Ubuntu 10.2-1.pgdg16.04+1)". In other words the
> version returned is not "parsed/cleaned", and if you need to
> implement some logic based on the version, is better to use
> getDatabaseMajorVersion() and getDatabaseMinorVersion().
>
> Regards.
>
> On Mon, Feb 19, 2018 at 9:52 AM, Thomas Kellerer <spam_eater@gmx.net <mailto:spam_eater@gmx.net>> wrote:
>
> I have just noticed that DatabaseMetaData.getDatabaseProductVersion() returns the String "10.2.2" when connected
toa server running on Ubuntu, but returns "10.2" when connected to a server running on CentOS or Windows.
>
> Is there a specific reason for this?
>
> It's a bit confusing because 10.2.2 doesn't actually exists as a "real" Postgres version.
>
> This happens with the driver versions 42.1.4 and 42.2.1 (haven tried others)
>
> Regards
> Thomas
>
>
>
>
