Re: smart shutdown at end of transaction (was: Default mode for shutdown) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: smart shutdown at end of transaction (was: Default mode for shutdown)
Date
Msg-id 1335721706.12058.22.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: smart shutdown at end of transaction (was: Default mode for shutdown)  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: smart shutdown at end of transaction (was: Default mode for shutdown)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On sön, 2012-04-29 at 10:19 +0100, Simon Riggs wrote:
> Maybe we don't need to do this over multiple releases, but we do need
> to give warning of possible incompatibilities. It would be good to see
> a specific post on hackers called "Planned Incompatibilities in 9.2",
> or collect such things on the open items wiki, so that people
> listening can see what might happen and get a chance to object. Or if
> changes do go ahead, at least we give them a few months warning to
> change the downstream software. Otherwise all that happens is our new
> release comes out and fewer people use it because it takes ages to
> actually realign the software stack enough for our software to be
> used.

Well, either there are possible incompatibilities, in which case users
will be slow to adopt new releases, as is currently the case, or there
strictly won't be any (unless hidden behind config settings or similar),
but then introducing new features or bug fixes can take many years.  So
far we've erred on the side of "progress".




pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: default_transaction_isolation = serializable causes crash under Hot Standby
Next
From: Peter Eisentraut
Date:
Subject: precision and scale functions for numeric