Make more use of RELKIND_HAS_STORAGE()
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]/messages/by-id/dc35a398-37d0-75ce-07ea-1dd71d98f8ec@2ndquadrant.com, but it seems worth
moving forward independently.
[0]: /messages/by-id/dc35a398-37d0-75ce-07ea-1dd71d98f8ec@2ndquadrant.com
/messages/by-id/dc35a398-37d0-75ce-07ea-1dd71d98f8ec@2ndquadrant.com
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachments:
0001-Make-more-use-of-RELKIND_HAS_STORAGE.patchtext/plain; charset=UTF-8; name=0001-Make-more-use-of-RELKIND_HAS_STORAGE.patch; x-mac-creator=0; x-mac-type=0Download+31-56
Peter Eisentraut <peter.eisentraut@2ndquadrant.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.
regards, tom lane
On 2020-06-05 18:05, Tom Lane wrote:
Peter Eisentraut <peter.eisentraut@2ndquadrant.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
