The discussion revolves around a version mismatch issue when backing up a Discourse instance connected to an external AWS RDS PostgreSQL 11.x database. thomas_grice reports a backup failure due to the container’s pg_dump version (10.10) being incompatible with the server version (11.5). Falco confirms that the supported PostgreSQL version is 10.x, with plans to upgrade to 12.x in the near future, skipping 11.x. GavinGCP notes that Google Cloud Platform defaults to PostgreSQL 11, prompting questions about support and downgrade options. Falco reassures that PostgreSQL 11 should function otherwise, except for backup and restore, which rely on the container’s pg_dump. reidab shares a workaround using update-alternatives to switch to PostgreSQL 11’s pg_dump. sam confirms that upgrading to PostgreSQL 12 in official images is planned. Falco also points to a meta.discourse.org post about PostgreSQL 12 availability on AWS RDS.
Hi, I’m configuring an environment that is pointed at an external AWS rds instance (postgres 11.x)
I notice this error when trying to backup through the UI:
[2019-10-25 21:50:35] Dumping the public schema of the database...
[2019-10-25 21:50:35] pg_dump: server version: 11.5; pg_dump version: 10.10 (Debian 10.10-1.pgdg100+1)
[2019-10-25 21:50:35] pg_dump: aborting because of server version mismatch
I guess this is because the docker container’s pg_dump version is not matching the version of the external rds database. Any suggestions on how to deal with this? Should I just use an external db that isn’t 11.x?
We deployed on postgres 11 already.
Can we continue using?
Is backup the only feature not working?
How to downgrade to 10, if we can not export/import?
As PostgreSQL is very solid on keeping features working and not trigger happy with removing features it should work, except for the backup and restore which depends on the container pg_dump version.
We don’t run it, and don’t test on it, so you are on your own if any problem arises.