pgsql: Run perltidy over Catalog.pm

From: John Naylor <john(dot)naylor(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Run perltidy over Catalog.pm
Date: 2022-09-08 07:02:30
Message-ID: E1oWBYT-001xjQ-WC@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Run perltidy over Catalog.pm

Commit 69eb643b2 deliberately left indentation unchanged to make the changes
more legible. Rather than waiting until next year's perltidy run, do it now
to avoid confusion

Per suggestion from Álvaro Herrera
Discussion: https://www.postgresql.org/message-id/20220907083558.vfvb5hcauaictgum%40alvherre.pgsql

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b2e6e768230be334b12dae536ba4c147fba4e9c9

Modified Files
--------------
src/backend/catalog/Catalog.pm | 111 +++++++++++++++++++++--------------------
1 file changed, 56 insertions(+), 55 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message John Naylor 2022-09-08 07:07:56 pgsql: Add b2e6e7682 to .git-blame-ignore-revs
Previous Message John Naylor 2022-09-08 06:57:37 pgsql: Parse catalog .dat files as a whole when compiling the backend