Closed oukanghua closed 8 months ago
Not sure what the exact problem is, but I guess something to do with pg_cron
.
There's a required postgres parameters cron.database_name
for postgres. check that.
Maybe you can remove that extensions and shared libraires, and install it after cluster is bootstrapped.
Not sure what the exact problem is, but I guess something to do with
pg_cron
.There's a required postgres parameters
cron.database_name
for postgres. check that.Maybe you can remove that extensions and shared libraires, and install it after cluster is bootstrapped.
Thank you for your answer. I found the parameter of ‘pg_extensions’ is mismatched.Final configuration is
pg_extensions:
- pg_repack_${pg_version}* wal2json_${pg_version}* passwordcheck_cracklib_${pg_version}*
- postgis3*_${pg_version}* timescaledb-2-postgresql-${pg_version}* pgvector_${pg_version}* citus_${pg_version}*
- pg_jobmon_${pg_version}* hll_${pg_version}* topn_${pg_version}* tdigest_${pg_version}*
1. The Installation Log
2. pigsty.yml
3. patroni status
4. patroni log