From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: retire MemoryContextResetAndDeleteChildren backwards compatibility macro |
Date: | 2023-11-14 19:20:08 |
Message-ID: | 202311141920.edtj56saukiv@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2023-Nov-14, Nathan Bossart wrote:
> On Tue, Nov 14, 2023 at 12:10:41PM -0500, Tom Lane wrote:
> > FWIW, I think it's fine to just nuke MemoryContextResetAndDeleteChildren.
> > We ask extension authors to deal with much more significant API changes
> > than that in every release, and versions where the updated code wouldn't
> > work are long gone. And, as you say, the existence of that separate from
> > MemoryContextReset creates confusion, which has nonzero cost in itself.
>
> That is my preference as well. Alvaro, AFAICT you are the only vote
> against removing it completely. If you feel ѕtrongly about it,
Oh, I don't. (But I wouldn't mind putting pg_attribute_deprecated to
good use elsewhere ... not that I have any specific examples handy.)
Your S key seems to be doing some funny business.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Hay dos momentos en la vida de un hombre en los que no debería
especular: cuando puede permitírselo y cuando no puede" (Mark Twain)
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2023-11-14 19:28:50 | Re: Why do indexes and sorts use the database collation? |
Previous Message | Nathan Bossart | 2023-11-14 17:59:53 | Re: retire MemoryContextResetAndDeleteChildren backwards compatibility macro |