Re: Remaining calls of heap_close/heap_open in the tree - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Remaining calls of heap_close/heap_open in the tree
Date
Msg-id 20191017095827.GA22713@alvherre.pgsql
Whole thread Raw
In response to Re: Remaining calls of heap_close/heap_open in the tree  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Remaining calls of heap_close/heap_open in the tree
List pgsql-hackers
On 2019-Oct-17, Michael Paquier wrote:

> On Thu, Oct 17, 2019 at 01:04:50AM -0700, Andres Freund wrote:
> > Wonder if it's worth removing the backward compat ones from master? I
> > don't quite think so, but...
> 
> I would vote for the removal so as we'll never see that again in
> core.  Let's see what others think here.

Agreed.  There are enough other API changes that if an external
extension wants to keep using heap_* in their code, they can add their
own defines anyway.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: v12.0: segfault in reindex CONCURRENTLY
Next
From: Madars Vitolins
Date:
Subject: Memory leak reported by address sanitizer inECPGconnect/CRYPTO_zalloc