When starting Vaultwarden with a fresh postgresql backend -- does vaultwarden create the table structure?

I’m currently using three VW containers with three different backends – sqlite, mysql and postgresql. The postgresql container is at version 11.4. What I’m really doing is trying to figure out a way to upgrade from version 11.4 to postgres 16. Per postgres documentation it looks possibly like a pgdumpall command is probably the best way to accomplish this. I’m kind of stuck however since if I spin up a new postgres16 container, the container never really starts. I’m stuck with this in the logs:

postgresql 09:36:41.20 INFO  ==>
postgresql 09:36:41.20 INFO  ==> Welcome to the Bitnami postgresql container
postgresql 09:36:41.20 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 09:36:41.20 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 09:36:41.20 INFO  ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
postgresql 09:36:41.21 INFO  ==>
postgresql 09:36:41.21 INFO  ==> ** Starting PostgreSQL setup **
postgresql 09:36:41.24 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql 09:36:43.15 INFO  ==> Cleaning stale /bitnami/postgresql/data/postmaster.pid file
postgresql 09:36:43.16 INFO  ==> Loading custom pre-init scripts...
postgresql 09:36:43.16 INFO  ==> Initializing PostgreSQL database...
postgresql 09:36:43.23 INFO  ==> pg_hba.conf file not detected. Generating it...
postgresql 09:36:43.23 INFO  ==> Generating local authentication configuration
postgresql 09:36:43.51 INFO  ==> Deploying PostgreSQL with persisted data...
postgresql 09:36:43.53 INFO  ==> Configuring replication parameters
postgresql 09:36:43.57 INFO  ==> Configuring fsync
postgresql 09:36:43.58 INFO  ==> Configuring synchronous_replication
postgresql 09:36:43.62 INFO  ==> Loading custom scripts...
postgresql 09:36:43.62 INFO  ==> Loading user's custom files from /docker-entrypoint-initdb.d ...
postgresql 09:36:43.62 INFO  ==> Starting PostgreSQL in background...

Curious what I do at this point since clearly I don’t get a statement about it listening. On my working 11.4 container, I have log lines stating:

2024-06-21 17:23:51.241 CDT [1] LOG:  pgaudit extension initialized
2024-06-21 17:23:51.241 CDT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-06-21 17:23:51.241 CDT [1] LOG:  listening on IPv6 address "::", port 5432
2024-06-21 17:23:51.272 CDT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2024-06-21 17:23:51.362 CDT [96] LOG:  database system was shut down at 2024-06-21 17:19:11 CDT
2024-06-21 17:23:51.397 CDT [1] LOG:  database system is ready to accept connections
2024-06-21 17:24:07.009 CDT [122] LOG:  standby "walreceiver" is now a synchronous standby with priority 1
2024-06-21 17:24:07.009 CDT [122] STATEMENT:  START_REPLICATION 0/5000000 TIMELINE 1

Any suggestions?