Tim Stevens (Jul 07 2025 at 16:01): Tim Stevens (Jul 07 2025 at 16:01):Greeting All,
In order to outrun the impending EOL for PG13 we are moving to PG15 ( cant go to 16 yet due to other institutional factors ). How do the new public schema changes in 15 effect how I would migrate the data relative to (pg_dump) process or config file changes? Thanks for any input, advice or potential gotcha's
Oliver Bertuch (Jul 08 2025 at 13:38):I have just recently played with running the DB upgrades outside of a deployment and presented my experiments during DCM2025. Maybe that's something you can play with, too? Here are my slides: http://talks.bertuch.name/dcm2025-upgrade
Philip Durbin 🚀 (Jul 08 2025 at 13:45):If it helps, #9877 is the PR where we updated the installer to GRANT ALL ON SCHEMA public to the pguser. And we added a related note to the guides.
Tim Stevens (Jul 09 2025 at 12:59):Thanks Oliver ( nice presentation by the way ) and Phil. All went smoothly and our staging instance is now using PG15. Since the installer was not involved in this move I was not sure if the GRANT ALL would carry over.
Philip Durbin 🚀 (Jul 09 2025 at 13:02):Hmm, so you didn't need the GRANT ALL, it sounds like. :thinking:
Tim Stevens (Jul 09 2025 at 13:10):I did a basic pg_dump on the PG13 db and used command line psql command to import it into an empty PG15 db on our RDS PG15 datastore. The dvndb user owns the db within the datastore so perhaps the GRANT ALL is implied?
Philip Durbin 🚀 (Jul 09 2025 at 13:11):Maybe. Or maybe that GRANT ALL is only needed during the installation process? I think I remember it failing without it. Not sure. 
Tim Stevens (Jul 09 2025 at 13:13):Im adding it to my notes as a "be aware of and verify". Thanks Phil, will mark this as resolved.
Notification Bot (Jul 09 2025 at 13:18):Tim Stevens has marked this topic as resolved.
Philip Durbin 🚀 (Jul 09 2025 at 13:50):Thanks, Tim. For the record, it looks like we switched the installer from GRANT ALL to GRANT CREATE in #9903.
Last updated: Oct 30 2025 at 06:21 UTC