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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/b060f57791cfd84ec7c7eb84eb1d1d38b39aa0a5 Modified Files -------------- src/backend/catalog/Catalog.pm | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-)
