PostgreSQL / pgAdmin4 / dump server version mismatch using docker images - postgresql

My environment is using the following docker images:
postgres:11
dpage/pgadmin4
On a machine using unRaid for it's OS.
My issue is that I'm unable to backup anything on my postgres 11 server via pgadmin4. pgadmin4 returns the following error:
pg_dump: server version: 11.2 (Debian 11.2-1.pgdg90+1); pg_dump version: 10.5
pg_dump: aborting because of server version mismatch
There was a similar question asked here: PostgresSQL / pgAdmin4 / dump server version mismatch
They resolved in by changing the bin path, however these are docker images, and I am unable to find standalone binary file for Postgres 11 for Linux.
There is a issue in relation to this exact problem, but it was rejected and closed: https://redmine.postgresql.org/issues/3843
I'm looking for any assistance to get/replace the tools in pgadmin4 so it can properly talk to postgres11.

Turns out the solution for now is to use the snapshot build of pgadmin4's docker image.
It had something to do the tools available in Alpine Linux's docker image at the time, according to Dave Page, the maintainer of pgadmin4's docker images. They were updated recently and used in the snapshot image's build.

Whoever packaged the pgAdmin 4 you are using packaged it with a PostgreSQL v10 client.
So that's where you'll have to complain.
In this case it is obviously Dave Page.
The website of the Docker image (https://hub.docker.com/r/dpage/pgadmin4/) suggests:
Please report any issues through the pgAdmin support channels. See https://www.pgadmin.org/support/list/
So I guess the correct channel is to subscribe to that mailing list and voice your complaint there.
Sorry that this is so complicated, but the various tools in the PostgreSQL universe are maintained by different, albeit somewhat related, groups, each of which has its own channels.

Related

AWS RDS PostgreSQL Upgrade from 9.6.22 to 10.17

Good day. I just finished upgrading my AWS RDS database engine from 9.6.22 to 10.17. I used these steps to make the upgrade using the AWS Console:
Create snapshot of target database to upgrade
Restore snapshot
Upgrade the restored snapshot's (which is now a new instance) DB Engine version.
After I did all of this, everything seems fine but when I access the database, this warning message appears
WARNING: psql major version 9.6, server major version 10.
Some psql features might not work.
I did not continue on my testing because I want to know what is the meaning of this first. Because I am fairly new in AWS as a whole. Thanks!
The meaning is that just because you are connecting to an upgraded database on some machine run by Amazon, the PostgreSQL installation on your local machine was not magically updated. psql from version 9.6 doesn't know what metadata tables were changed in v10, what features were removed and so on.
It would be a good idea to install a more recent version of PostgreSQL on your machine. By the way, upgrading to v10 was not the smartest move, as that version will go out of support in less than a year. You should upgrade to the latest version that your service provider offers.
The client program psql you are using to connect to the database is from an older version than the database it is connecting to. Some of the introspection features might not work. For example, psql from 9.6 won't know how to do tab completion for commands that were added to the server after 9.6.
This is generally not a major problem for psql (unless the server wants to use SCRAM authentication), but for optimal experience it would be good to install a newer client. Other tools like pg_dimp might not with at all against a server newer than they are.

Db2 pull docker image and Trial version Db2 Binary comparison

I have a Db2 11.5 Trial Version image for installing db2 on RHEL7. I have no connectivity with the internet where docker installed and I want to configure db2 on docker with that 11.5 Trial Version image.
Is there any limitation to use only docker certified image for dockerization?.
There's no requirement that you use IBM's docker images when running Db2 in Docker. You can absolutely build your own Docker images from the standard installable code.
However, are you aware that you can "export" Docker images to using docker save and "import" them using docker import? This is certainly one way you could get IBM's official docker images on to a machine that does not have direct internet access.

Install PostgreSQL 11.1 on Debian Stretch with PostgreSQL Debian (9.6)

I have a production machine running debian strecth that I do not want to mess up. I have an app that requires postgres 11 and I'm not sure about a thing. Does the installation from the official postgres debian repo install as an extra server or does it replace the existing 9.6 verssion on debian?
I have tried to dump from version 11 and restore in 9.6 but it throws an error on creation of a sequence:
psql:fas-schema.sql:125: ERROR: syntax error at or near "AS"
LINE 2: AS integer
Just need to be sure 100%
If you want to run multiple versions of PostgreSQL one the same host, you should use official packages provided by PGDG. All the currently supported versions are available.
Though, these packages are not including tools provided by the Debian project, such as pg_ctlcluster or pg_lsclusters.

How to fix pg_dump: aborting because of server version mismatch

My codebase and database is hosted on different servers with Ubuntu 12.04.
database => web1
codebase => web2
I am trying to take my database backup (web1) through the application(web2).
Now the problem is I have different versions of postgres installed on web1 and web2.
pg_dump: server version: 9.3.12 (web1)
pg_dump version: 9.1.23 (web2)
Is there any way I can resolve this issue without upgrading any package because there are multiple applications hosted and relying on these versions.
Thanks for helping!
pg_dump will refuse to connect to a server with a later version than itself for the good reason that it cannot guarantee that it will work.
Downgrading a database from 9.3 to 9.1 is definitely not supported, particularly since version 9.1 is out of support.
You'll have to use pg_dump from the 9.3 installation to dump the database, then you can try to load the result into the 9.1 database. Watch out for errors during restore and test well!
If you are using a SQL Client like Dbeaver and have more than one version of Postgres, remember to change the client version in the option. I was getting this error while using the Dbeaver's backup tool.

unable to locate postgresql in etc centos

I tried installing postgresql in my server which has centos
I followed this link
I am facing few complexity here.
I could not locate postgresql file in /etc directory.
psql (8.4.13, server 9.2.4) WARNING: psql version 8.4, server version 9.2. Some psql features might not work.
How can i solve these issues. can anyone suggest me.
I could not locate postgresql file in /etc directory.
The tutorial you linked to suggests the config files are in /var/lib/pgsql/9.2/data/...
psql (8.4.13, server 9.2.4) WARNING: psql version 8.4, server version 9.2. Some psql features might not work.
You've still got the 8.4 version of psql installed. Use your package tools (rpm/yum) to see what versions of the psql client packages are installed and where the binaries are.
It's common enough to run two different versions of PG on the same machine. Obviously each needs its own data directory and port number. Also, as you've seen psql will check the version number and warn if they are different. Basic queries still work, but obviously an 8.4 version won't know about extensions introduced in 9.1 and that sort of thing.