Slight refactoring of state check in pg_upgrade check_ function

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Slight refactoring of state check in pg_upgrade check_ function
Date: 2022-08-28 20:42:24
Message-ID: 595759F6-625B-4ED7-8125-91AF00437F83@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I noticed that the pg_upgrade check_ functions were determining failures found
in a few different ways. Some keep a boolen flag variable, and some (like
check_for_incompatible_polymorphics) check the state of the script filehandle
which is guaranteed to be set (with the error message referring to the path of
said file). Others like check_loadable_libraries only check the flag variable
and fclose the handle assuming it was opened.

The attached diff changes the functions to do it consistently in one way, by
checking the state of the filehandle. Since we are referring to the file by
path in the printed error message it seemed the cleanest approach, and it saves
a few lines of code without IMO reducing readability.

There is no change in functionality, just code consistency.

--
Daniel Gustafsson https://vmware.com/

Attachment Content-Type Size
v1-0001-Refactor-check_-functions-to-use-filehandle-for-s.patch application/octet-stream 7.5 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-08-28 21:14:21 Re: replacing role-level NOINHERIT with a grant-level option
Previous Message Andres Freund 2022-08-28 20:37:41 Re: [RFC] building postgres with meson - v12