Here is a thread on this, maybe would help some geeks :)

https://stackoverflow.com/questions/59455783/pg-restore-archiver-unsupported-version-1-14-in-file-header

Another hints from Stackoverflow:

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.

Archive version 1.13 was introduced by commit 3d2aed664ee8271fd6c721ed0aa10168cda112ea in February 2018. It has been available since the point releases 10.3, 9.6.8, 9.5.12, 9.4.17 and 9.3.22.

You should upgrade your PostgreSQL installation, particularly because this release and this patch contain security relevant bug fixes.

https://stackoverflow.com/questions/55234984/pg-restore-archiver-unsupported-version-1-13-in-file-header

Another hint:

I purged PostgreSQL 10 completely, and installed v. 11, thinking that maybe the newer version of pg_restore (11.11) could deal with this 1.14, but to no avail.

Same output, unsupported version in file header.

Does anyone know which version of PostgreSQL should I install to deal with 1.14 as above?

There is probably nothing in the internet. Usual fix is to upgrade postgresql. That does not help so far.

Just to make sure, in those OP versions

11.2.0 - 11.2.2

was used the same postgresql version, ie. 10.16?

If so, it would be very strange, that a dump created by 10.16 returns pg_restore 1.14, and cannot be restored by the same version of postgresql.

Hi Piotr,

right now, OpenProject installs the latest stable postgres server version 10, which would be 10.16. I can't reproduce this error when dumping from 10 and restoring in a newer version. Are you sure you were not running a newer version of postgres yourself?

Best

Oliver

Hi Oliver,

Absolutely not, I have realized that another postgresql versions exist just recently, when having the newest problems. :)

Definitely everything was very default, I used only your upgrade and configure commands.

It is odd, because now, as mentioned, I can create a dump, and restore it, no problem.

Also, I have restored OLDER dump to full success, which is a life saver, I am going to buy a nice Riesling in an hour. :)

The backup created on April 8 worked with pg_restore, while this one from April 12 did not! This is really strange.

My guess is, postgresql released some not-so-good version of pg_dump 1.14, which was incidentally deployed for some time.

Cheers,

Piotr

Hi Piotr,

My guess is, postgresql released some not-so-good version of pg_dump 1.14, which was incidentally deployed for some time.

That might indeed be the case, however I'd expect more people to be affected by this then. The pg_dump format is a bit picky with regards to versioning, more than we probably need. So we could evaluate whether to simply export a plain SQL dump in all cases.

Best

Oliver

Oliver Günther wrote:

The pg_dump format is a bit picky with regards to versioning, more than we probably need. So we could evaluate whether to simply export a plain SQL dump in all cases.

Hi Oliver,

Exactly, thought the same. In such cases, there is a chance to edit text file at least (to my limited knowledge, that's what Internet says).

Or, you might want to give a choice when issuing a command

1. pgdump
2. sql dump
3. both.

Anyway, the problem persists, and it might be dangerous in the future. Postgresql replied so far that I had to use pg_restore older than the pg_dump, which is not the case. It is odd, because it looks the opposite, or, most possibly, I used the same 10.16 versions in all the cases.

Cheers,

Piotr