How to know pg_ restore version?
You can check the pg_restore version you’re using by running pg_restore –version. If you are using a third-party tool, such as PgAdmin, to restore the provided dump file, the restore may not succeed even with the installed Postgres version being up to date.
What is my Postgres version?
Check Postgres Version from SQL Shell Type the following SQL statement within the prompt to check the current version: SELECT version(); The resulting output provides the full version and system information for the PostgreSQL server.
Why is PostgreSQL-PG _ restore unsupported version ( 1 )?
This error means that you are using an old and outdated version of pg_restore (and hence PostgreSQL) on the client side. The dump was created by a more recent release of PostgreSQL that the one installed, so your pg_restore does not know how to handle it.
Why does PostgreSQL not restore an archive file?
Since this change requires a change in the behavior of pg_restore when processing an archive file made according to this new convention, bump the archive file version number; old versions of pg_restore will therefore refuse to process files made with new versions of pg_dump.
How to run PG _ restore [ archiver ] unsupported version?
Here’s what it does: If –host is provided then it uses the newest version of postgresql installed (12 in my case and this is for pg_dump, so pg_dump 12 creates the dump) If –host is not provided then it consults the user config (10 in my case, and this is for pg_restore, so pg_restore 10 is run and it can’t read a file created by pg_dump 12).
Which is unsupported version of PG _ dump archive format?
Restore: pg_restore: [archiver] unsupported version (1.13) in file header Version 1.13 of the pg_dump archive format was introduced in February 2018 as part of the changes for CVE-2018-1058 . The version bump was mentioned in the commit message with a specific warning about the problem: