Make eval statement naturally proof against perltidy
authorJohn Naylor <john.naylor@postgresql.org>
Mon, 12 Sep 2022 04:59:43 +0000 (11:59 +0700)
committerJohn Naylor <john.naylor@postgresql.org>
Mon, 12 Sep 2022 04:59:43 +0000 (11:59 +0700)
commitb060f57791cfd84ec7c7eb84eb1d1d38b39aa0a5
tree7900e4119ea502c90387704ee4a4d07897b1aa89
parentc3fb5809eae3bb6f448ebc562462b39d6b1f6f22
Make eval statement naturally proof against perltidy

This is a bit less verbose than adding an exception. Rewrite
the other eval statement in Catalog.pm as well, just for
the sake of consistency.

Idea from Andrew Dunstan
Discussion: https://www.postgresql.org/message-id/CAD5tBc%2BzRhuWn_S4ayH2sWKe60FQu1guTTokDFS3YMOeSrsozA%40mail.gmail.com
src/backend/catalog/Catalog.pm