pg_repack workers ignore --elevel= value from command line and runs with --elevel=log

[MaximBoguk]

pg_repack workers ignore --elevel= values and run with --elevel=log

sample:

pg_repack --table=job_stats_new_2026_02 --elevel=WARNING --dbname=redacted
--no output

vs
pg_repack --table=job_stats_new_2026_02 --elevel=WARNING --jobs=4 --dbname=redacted
LOG: Initial worker 0 to build index: CREATE INDEX index_3436771073 ON repack.table_3371668452 USING btree (parent_job_id) WHERE (parent_job_id IS NOT NULL)
LOG: Initial worker 1 to build index: CREATE INDEX index_3371668463 ON repack.table_3371668452 USING btree (job_posting_id) WHERE (job_posting_id IS NOT NULL)
... and so on with a log noise in logs/cron emails without actual errors during run

[za-arthur]

@MaximBoguk thank you for the report!

It seems it isn't specific to workers. For some reason LOG level has higher precedence that WARNING:

pg_repack/bin/pgut/pgut.c

Line 954 in 85b64c6

* DEBUG < INFO < NOTICE < WARNING < ERROR < LOG < FATAL < PANIC

[za-arthur]

Apparently LOG messages shouldn't be used by client side of pg_repack since LOG messages are considered server side messages. PR to replace LOG to INFO:
#479

[za-arthur]

Fixed by #479

[MaximBoguk]

Thank you.