"Tick-tock" release cadence?

[M. Edward (Ed) Borasky]

On Fri, Dec 5, 2014 at 10:25 PM, Kevin Kofler <kevin.kofler at chello.at> wrote:
> And unfortunately, a new PostgreSQL IS incompatible, because if you just run
> "yum update", your databases will cease to work. You have to actually dump
> them BEFORE doing the upgrade (or downgrade PostgreSQL for the dump, or
> install the old version in parallel, which is not supported by the RPMs),
> then do the upgrade, and then import the dump. As long as upstream does not
> change this migration policy, it will NEVER be possible to provide newer
> PostgreSQL release series un updates.

I thought PostgreSQL fixed that a couple of years ago - "upgrade in
place" was the most-requested feature for a long time. But I can see
why DBAs wouldn't trust it after having mastered the
dump-upgrade-restore process.