On 2015-02-26 18:05:46 -0500, Tom Lane wrote: > Andres Freund <and...@2ndquadrant.com> writes: > > On 2015-02-26 17:45:26 -0500, Tom Lane wrote: > > If the changes breaks some code it's likely actually a good thing: > > Because, as you say, using MemoryContextReset() will likely be the wrong > > thing, and they'll want to fix it for the existing branches as well. > > Is that likely to happen? I doubt it. They'll just mutter under their > breath about useless API breakage and move on.
Maybe. > Basically, this is a judgment call, and I disagree with your judgment. Right. That's ok, happens all the time. > And I've got to say that I'm losing patience with > backwards-compatibility arguments taken to this degree. We might as > well stop development entirely. Meh, normally you're on the side I'm on right now... Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
