Robert Haas <robertmh...@gmail.com> writes: > As has already been pointed out, it could definitely happen, but we > could solve that by just using a longer version number, say, including > the month and, in case we ever do multiple major releases in the same > month, also the day. In fact, we might as well take it one step > further and use the same format for the release number that we use for > CATALOG_VERSION_NO: YYYYMMDDN. So this fall, piggybacking on the > success of PostgreSQL 10, 11, and 12, we could look then release > PostgreSQL 202009241 or so.
But then where do you put the minor number for maintenance releases? regards, tom lane