zalando / spilo

Highly available elephant herd: HA PostgreSQL cluster using Docker
Apache License 2.0
1.53k stars 382 forks source link

pgqd won't start in new build because the latest version doesn't allow invalid entries in pgd_ticker.ini #838

Closed mblsf closed 1 year ago

mblsf commented 1 year ago

When creating a new build of the spilo docker image, the pgqd won't start because the latest version of pgqd, which is fetched during the build, doesn't allow invalid entries in pgd_ticker.ini

The following error messages will be written over and over again to stdout: ERROR unknown parameter: pgqd/job_name
ERROR invalid value "ticker" for parameter job_name in configuration (/home/postgres/pgq_ticker.ini:2)
FATAL @src/pgqd.c:88 in function load_config(): failed to read config

mblsf commented 1 year ago

Additional information about the parameters:

job_name: parameter has been removed

maint_delay: renamed to maint_period loop_delay: renamed to ticker_period

logfile: new mandatory parameter pidfile: new mandatory parameter

ngocannguyen02 commented 1 year ago

+1 Same

hughcapet commented 1 year ago

Oh, there is indeed a problem with pgqd. Thank you for reporting

wuputah commented 1 year ago

Is pgqd used by anything internally to the spilo stack, or is it present to complete and support the pgq extension? I can't conclusively determine why it's part of the image.

hughcapet commented 1 year ago

The second one, it is provided as a part of the pgq support