Re: PG_VERSION_NUM formatted incorrectly
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Kieran McCusker <kieran.mccusker@gmail.com>,
pgsql-bugs@lists.postgresql.org
Date: 2018-01-22T19:14:41Z
Lists: pgsql-bugs
Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > Kieran McCusker wrote: >> But shouldn't it be >> #define PG_VERSION_NUM 100100 > You're not being dense -- the way we're using it is indeed a bit odd. > But it was a concious decision to leave it like this: the reason is that > we've been using these two digits to indicate patch level rather than > major for so long, that is seems less likely to break version parsing > tools if we continue to do that. So the patch level for release 10 is > going to use the last two digits only, with the two middle digits > remaining constant 00 forever. Right. If we did it the other way, much code would think that 10.1 is a new major version, not a new minor version. regards, tom lane