"Jonathan S. Katz" <jk...@postgresql.org> writes: > Perhaps instead of "June" it could be the specific version number (which > could cause some pain with the back branching?) or the "2019-06-20" release?
Putting in all the version numbers seems like a mess, but specifying
2019-06-20 would work --- or we could say "the most recent" minor
releases?
regards, tom lane
