pg_dump not dumping config table data

[redrick]

We ran into issue when we dump our DBs like:

pg_dump -F p <database>

and after restore of this dump we have no data in amqp.broker table.

I can understand the logic of ti, why it is empty thou...

Not ideal for our situation where we have multitenant app and create daily tens of DBs from dump of default DB...

Now we found ourselves with coule DBs that are unable to post to AMQP and since DB creation is completely automated and adding new steps is not really feasible for us, I will submit PR shortly where I basically propose moving it from DB table to postgresql.conf, which we already use for universal configuration extensively and is proven to work at least for us.

Please see docs in PR, I kept the format of the table so for extension there is basically no change.

Thank you for your time 😄

[Godwottery]

I can not replicate this. My dump file has the content of amqp.broker in it. Perhaps there is something wrong with your restoration process.

[xzilla]

After some discussion between @vventirozos and myself, ISTM the correct answer is to set the config tables as "dumpable" in the extension. See https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSIONS-CONFIG-TABLES more more information on this. I think @vventirozos has committed a fix, we'd be interested in a few +1 before closing this, but this seems like the likely path forward.