| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | combit - Nicolaij Deutschkämer <Deutschkaemer(at)combit(dot)net>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Incompatibility of newest pg_restore with PostgreSQL-Servers older or equal to version 16 |
| Date: | 2024-12-18 14:25:40 |
| Message-ID: | 73f2a5f02921062ef1fe00bc07b4e431d7a8826f.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 2024-12-18 at 10:05 +0000, combit - Nicolaij Deutschkämer wrote:
> we are currently facing an issue regarding the usage of the latest pg_restore.exe from V17
> with PostgreSQL-Servers older or equal to version 16.
You cannot use pg_restore from v17 to restore into a v16 server.
In https://www.postgresql.org/docs/current/app-pgdump.html, we have:
"Also, it is not guaranteed that pg_dump's output can be loaded into
a server of an older major version — not even if the dump was taken
from a server of that version."
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-12-18 15:13:04 | Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory |
| Previous Message | combit - Nicolaij Deutschkämer | 2024-12-18 10:05:17 | Incompatibility of newest pg_restore with PostgreSQL-Servers older or equal to version 16 |