Re: [BUG FIX] Version number expressed in octal form by mistake

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Joel Jacobson <joel(at)trustly(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUG FIX] Version number expressed in octal form by mistake
Date: 2013-12-27 22:03:08
Message-ID: 1388181788.34724.YahooMailNeo@web122303.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joel Jacobson <joel(at)trustly(dot)com> wrote:

> As reported by Andrey Karpov in his article
> http://www.viva64.com/en/b/0227/
> the version number is expressed in octal form 070100 should be
> changed to 70100.
>
> Attached patch fixes the reported issue.

This is a bug, but it's not clear what the correct patch should be.
If you look at our docs:

http://www.postgresql.org/docs/devel/static/app-pgdump.html#PG-DUMP-NOTES

It says, "(Currently, servers back to version 7.0 are supported.)"
The source code seems to be trying to support back to 7.1.0, but
because of the leading zero making it an octal literal it is taken
as version 2.87.36.  Do we want to make the code match the docs, or
make both match what the code appears to have been attempting?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Adrian Klaver 2013-12-27 22:07:51 Re: pg_upgrade & tablespaces
Previous Message Joseph Kregloh 2013-12-27 21:56:53 Re: pg_upgrade & tablespaces