Re: Make more use of RELKIND_HAS_STORAGE()

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Make more use of RELKIND_HAS_STORAGE()
Date: 2020-06-12 07:16:04
Message-ID: eb3acc83-a751-b609-f572-d1c1f6bae77b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-06-05 18:05, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> This is a patch to make use of RELKIND_HAS_STORAGE() where appropriate,
>> instead of listing out the relkinds individually. No behavior change is
>> intended.
>> This was originally part of the patch from [0], but it seems worth
>> moving forward independently.
>
> Passes eyeball examination. I did not try to search for other places
> where RELKIND_HAS_STORAGE should be used.

committed

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2020-06-12 07:17:37 Re: Internal key management system
Previous Message Michael Paquier 2020-06-12 07:08:26 Re: pg_upgrade fails with non-standard ACL