Upgrade problem

.so.1.1* -r-xr-xr-x  1 root root  442424 Feb 27  2021 libssl.so.1.0.0* -rwxr-xr-x  1 root root  666496 Jun  1 09:36 libssl.so.1.1* Can someone suggest my next move please? Ta Graeme Gemmill

Re: Upgrade problem

On 11/09/2023 17:10, Tom Lane wrote: Graeme writes: Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia 9/Pg 15. I'm at the point of running pg_upgrade but have received anerror message: /mga8/usr/bin/postgres: error while loading shared libraries: libssl.so.1.1: cannot

Re: Upgrade problem

On 11/09/2023 17:13, Adrian Klaver wrote: On 9/11/23 09:04, Graeme wrote: Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia 9/Pg 15. I'm at the point of running pg_upgrade but have received anerror message: You are going to have to be more specific on the Postgres ve

Re: Upgrade problem

On 11/09/2023 17:04, Graeme wrote: Preparing to upgrade my small cluster from Mageia 8/Pg 9 to Mageia 9/Pg 15. I'm at the point of running pg_upgrade but have received anerror message: /mga8/usr/bin/postgres: error while loading shared libraries: libssl.so.1.1: cannot open shared o

pg_update and encoding

Preparing to use pg_update, I used initdb to create the new pgsql/data, but pg_update has exited with encodings for database "template1" do not match:  old "UTF8", new "SQL_ASCII" Should I delete pgsql/data and re-create with initdb -E "UTF8"? Thanks, Graeme

Re: pg_update and encoding

On 12/09/2023 15:52, Adrian Klaver wrote: On 9/12/23 04:49, Graeme wrote: Preparing to use pg_update, I used initdb to create the new pgsql/data, but pg_update has exited with I'm guessing that is actually pg_upgrade: https://www.postgresql.org/docs/current/pgupgrade.html encoding

Use of Port 5433 with Postgresql 9.6

If the default port for v9.6 is 5433, why does the utility pg_isready still default to searching for 5432? Graeme

Re: Use of Port 5433 with Postgresql 9.6

have changed all port references to that. Regards Graeme

Query editor window not appearing

others? Regards, Graeme OFFICIAL

RE: Query editor window not appearing

OFFICIAL Just to update on this, I realised the window is actually present, it just needs to be maximised or resized and then the results of a query (Data Output) have to be switched to or resized etc - quite a different default to what I was used to, that's all. Graeme OFFICIAL