Re: Do away with a few backwards compatibility macros - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Do away with a few backwards compatibility macros
Date
Msg-id 20231116154622.GA2881373@nathanxps13
Whole thread Raw
In response to Do away with a few backwards compatibility macros  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Do away with a few backwards compatibility macros
List pgsql-hackers
On Thu, Nov 16, 2023 at 07:11:41PM +0530, Bharath Rupireddy wrote:
> After a recent commit 6a72c42f (a related discussion [1]) which
> removed MemoryContextResetAndDeleteChildren(), I think there are a
> couple of other backward compatibility macros out there that can be
> removed. These macros are tuplestore_donestoring() which was
> introduced by commit dd04e95 21 years ago and SPI_push() and friends
> which were made no-ops macros by commit 1833f1a 7 years ago. Debian
> code search shows very minimal usages of these macros. Here's a patch
> attached to remove them.

I'm fine with this because all of these macros are no-ops for all supported
versions of Postgres.  Even if an extension is using them today, you'll get
the same behavior as before if you remove the uses and rebuild against
v12-v16.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Alena Rybakina
Date:
Subject: Re: Wrong results with grouping sets
Next
From: Robert Haas
Date:
Subject: Re: pgsql: doc: fix wording describing the checkpoint_flush_after GUC