Slight refactoring of state check in pg_upgrade check_ function - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Slight refactoring of state check in pg_upgrade check_ function
Date
Msg-id 595759F6-625B-4ED7-8125-91AF00437F83@yesql.se
Whole thread Raw
Responses Re: Slight refactoring of state check in pg_upgrade check_ function
List 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

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [RFC] building postgres with meson - v12
Next
From: Nathan Bossart
Date:
Subject: Re: replacing role-level NOINHERIT with a grant-level option