Postgres Pro
Downloads
Home   >   mailing lists

Re: retire MemoryContextResetAndDeleteChildren backwards compatibility macro - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: retire MemoryContextResetAndDeleteChildren backwards compatibility macro
Date
Msg-id CALj2ACW2b=PLFVVLMSPOobBDLqj-tHDPfkO3HO36gxz0OSwq2w@mail.gmail.com
Whole thread Raw
In response to Re: retire MemoryContextResetAndDeleteChildren backwards compatibility macro  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
Tree view 
On Tue, Nov 14, 2023 at 11:29 PM Nathan Bossart
<nathandbossart@gmail.com> wrote:
>
> On Tue, Nov 14, 2023 at 10:46:25PM +0530, Bharath Rupireddy wrote:
> > FWIW, there are other backward compatibility macros out there like
> > tuplestore_donestoring which was introduced by commit dd04e95 21 years
> > ago and SPI_push() and its friends which were made no-ops macros by
> > commit 1833f1a 7 years ago. Debian code search shows very minimal
> > usages of the above macros. Can we do away with
> > tuplestore_donestoring?
>
> Can we take these other things to a separate thread?

Sure. Here it is -
https://www.postgresql.org/message-id/CALj2ACVeO58JM5tK2Qa8QC-%3DkC8sdkJOTd4BFU%3DK8zs4gGYpjQ%40mail.gmail.com.

--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Do away with a few backwards compatibility macros
Next
From: Heikki Linnakangas
Date:
Subject: Re: [HACKERS] Should logtape.c blocks be of type long?