Re: Remaining calls of heap_close/heap_open in the tree

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Remaining calls of heap_close/heap_open in the tree
Date: 2019-10-18 01:03:11
Message-ID: 20191018010311.GH17439@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 17, 2019 at 12:34:44PM +0100, Dagfinn Ilmari Mannsåker wrote:
> Would it be possible to wrap them in some #if(n)def guard so that
> they're available when building out-of-tree extensions, but not when
> building postgres itself?

Not sure that's worth the trouble. If there are no objections, I will
remove the compatibility macros.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-10-18 01:23:23 Re: v12.0: segfault in reindex CONCURRENTLY
Previous Message Stephen Frost 2019-10-17 22:02:57 Re: v12 and pg_restore -f-