Re: Renaming MemoryContextResetAndDeleteChildren to MemoryContextReset - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Renaming MemoryContextResetAndDeleteChildren to MemoryContextReset
Date
Msg-id 20150226230910.GA10102@awork2.anarazel.de
Whole thread Raw
In response to Re: Renaming MemoryContextResetAndDeleteChildren to MemoryContextReset  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2015-02-26 18:05:46 -0500, Tom Lane wrote:
> Andres Freund <andres@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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Renaming MemoryContextResetAndDeleteChildren to MemoryContextReset
Next
From: Jim Nasby
Date:
Subject: Re: logical column ordering