From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ian Barwick <barwick(at)gmx(dot)net> |
Cc: | dbi-dev(at)perl(dot)org, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Patch for DBD::Pg pg_relcheck problem |
Date: | 2002-12-09 23:47:30 |
Message-ID: | 20819.1039477650@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
Ian Barwick <barwick(at)gmx(dot)net> writes:
> So out with the candle wax and pins ;-). Am I right
> in thinking that the string returned by SELECT version()
> starts with the word "PostgreSQL" followed by:
> a space;
> a single digit indicating the major version number;
> a full stop / decimal point;
> a single digit indicating the minor version number;
> and either "interim release" number (e.g. ".1" in the case of 7.3.1), or
> "devel", "rc1" etc. ?
I would recommend parsing it the same way pg_dump does, see
_check_database_version(). Looks like it's basically skip-11-chars-
and-sscanf. Note the lack of assumptions about numbers of digits.
In the next protocol version update (hopefully 7.4) I would like to see
the basic version string (eg, "7.3.1" or "7.4devel") delivered to the
client automatically during connection startup and then available from a
libpq inquiry function. This would eliminate the need to call version()
explicitly and to know that you must skip "PostgreSQL " in its output.
However, it will only help for clients/libraries that are willing to
deal exclusively with 7.4-or-newer backends, so it will take a few
releases to become really useful.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-12-10 00:01:28 | Re: DB Tuning Notes for comment... |
Previous Message | Philip Warner | 2002-12-09 23:47:28 | Re: DB Tuning Notes for comment... |
From | Date | Subject | |
---|---|---|---|
Next Message | Godson Retna | 2002-12-10 13:23:58 | FATAL 1: Password authentication failed |
Previous Message | Ian Barwick | 2002-12-09 23:34:31 | Re: Patch for DBD::Pg pg_relcheck problem |