| Sorry, opened a little too early... this issue appears to relate to Postgresql module not the puppetdb module, I mis-created it by getting in too soon. I've now identified what looks like the root cause of the issue and it's not puppetdb module, it's the postgresql module. In Debian, for Postgresql-11 there is no 'real' postgresql-contrib-11 packages, it's been subsumed into postgresql package instead. postgresql-contrib is a virtual package that doesn't point to postgresql-contrib-11 but points to postgresql-11 instead. puppetlabs-postgresql module assumes for Debian that postgres-contrib requires version number appending to identify the package name and this isn't true for version 11 (was true for 9.6 and before). If 'params.pp' in puppetlabs-postgresql (version 6.2.0) at about line 175 is modified to only append version if it's not 11 (or perhaps below 11... who knows, Debian haven't packaged postgresql 12 yet)) issue is resolved. As are various other knock-on issues with the database restarting. For me the below worked... sorry, not diff, just edited the code... replacing line 175 with the block below it. #$contrib_package_name = pick($contrib_package_name, "postgresql-contrib-${version}")
if $version == "11" { $contrib_package_name = pick($contrib_package_name, "postgresql-contrib") } else {
$contrib_package_name = pick($contrib_package_name, "postgresql-contrib-${version}")
} May be neater for Debian / postgresql11 (the Buster default version of postgresql) to just skip that file, but that involves more understanding of the puppetlabs-postgresql module than I have. |
