What were you trying to do that didn't work?

Use postgresql container image with custom database and enabled extensions.

What is the impact of this issue to you?

Inconvinient development.

Please provide the package NVR for which the bug is seen:

postgresql-16-container-1-44

How reproducible is this bug?:

Always

Steps to reproduce

1. Start container image with both env variables set
2.  
3.  

Expected results

the created database has enabled extensions.

Actual results

extensions are enabled on the default postgres database and not on the newly created one.