> On 9 Feb 2024, at 00:04, Daniel Gustafsson <dan...@yesql.se> wrote: > >> On 8 Feb 2024, at 15:16, Daniel Gustafsson <dan...@yesql.se> wrote: > >> One option could perhaps be to include a version number for <= comparison, >> and >> if set to zero a function pointer to a version check function must be >> provided? >> That would handle the simple cases in a single place without messy logic, and >> leave the more convoluted checks with a special case function. > > The attached is a draft version of this approach, each check can define to run > for all versions, set a threshold version for which it runs or define a > callback which implements a more complicated check.
And again pgindented and with documentation on the struct members to make it easy to add new checks. A repetitive part of the report text was also moved to a single place. -- Daniel Gustafsson
v14-0001-pg_upgrade-run-all-data-type-checks-per-connecti.patch
Description: Binary data
