Hi, there is a mandatory schema upgrade when upgrading from 4.6.x to 4.7.0
https://doc.powerdns.com/authoritative/upgrading.html | The new Catalog Zones feature comes with a mandatory schema change for | the gsql database backends. See files named | 4.3.x_to_4.7.0_schema.X.sql Without it, it fails to start with: pdns[17775]: Exiting because communicator thread died with error: virtual void GSQLBackend::getUpdatedMasters(vector<DomainInfo> &, std::unordered_set<DNSName> &, CatalogHashMap &) unable to retrieve list of master domains: Fatal error during prePQpreparepare: select domains.id, domains.name, domains.type, domains.notified_serial, domains.options, domains.catalog, records.content from records join domains on records.domain_id=domains.id and records.name=domains.name where records.type='SOA' and records.disabled=false and domains.type in ('MASTER', 'PRODUCER'): ERROR: column domains.options does not exist LINE 1: ...ains.name, domains.type, domains.notified_serial, domains.op... Unfortunately the upstream tarball is missing 4.3.0_to_4.7.0_schema.pgsql.sql and 4.3.0_to_4.7.0_schema.mysql.sql so we also don't package it. I have reported this upstream: https://mailman.powerdns.com/pipermail/pdns-users/2022-October/027898.html The files are here: https://raw.githubusercontent.com/PowerDNS/pdns/master/modules/gpgsqlbackend/4.3.0_to_4.7.0_schema.pgsql.sql https://raw.githubusercontent.com/PowerDNS/pdns/master/modules/gmysqlbackend/4.3.0_to_4.7.0_schema.mysql.sql No idea how much effort it would be to carry them as a local patch to have them installed in /usr/local/share/doc/pdns/ Thanks, Florian -- I'm not entirely sure you are real.
