Help pg_restore version

On Sat, Sep 30, 2023, at 7:33 AM, Jorge Soro Domenech wrote:

But it show this error:

You didn't show the error message but I suspect it is:

pg_restore: [archiver] unsupported version (1.14) in file header

As you showed the first bytes in the dump file, that first information (11.18)
is the current Postgres version and the second one (15.2) is the pg_dump
version that you used to create that dump file. Since old pg_dump version might
not read a new format, you are getting this error. You can fix this issue using
the pg_restore from version 15.

PS> avoid images; prefer text error messages. It helps search engines to
completely index this message so others can find this discussion.

--
Euler Taveira
EDB https://www.enterprisedb.com/

Hello Euler,

thank you for your response.

The backup file has generated external enterprise that me.

You said i try import it backup file with pg_restore version 15, its
correct?

For a correct import, i need the version Postgree database i must have
(11.18) version but i need a pg_restore version 15 for import this "bak
file"

Its possible i have install Postgree database (11.18) and parallel i use
only a pg_restore version 15?

My sistem is a redhat unix.

This is the header backup file.

PGDMP % 6 { a121_prd_md_483100 11.18
15.2 _ 0 0 ENCODING ENCODING SET
client_encoding = 'UTF8';
false ` 0 0
STDSTRINGS
STDSTRINGS ( SET standard_conforming_strings = 'on';
false a 0 0
SEARCHPATH
SEARCHPATH 8 SELECT pg_catalog.set_config('search_path', '',
false);
false b 1262 449003
a121_prd_md_483100 DATABASE CREATE DATABASE a121_prd_md_483100
WITH TEMPLATE = template0 ENCODING = 'UTF8' LOCALE_PROVIDER = libc LOCALE =
'English_United States.1252';
" DROP DATABASE a121_prd_md_483100;
yya121mstrmddb false 2615
2200 public SCHEMA 2 -- *not* creating schema, since initdb
creates it
2 -- *not* dropping schema, since initdb creates it
yya121mstrmddb false ± 1255
449004 dssmdobjfunc() FUNCTION Ê CREATE FUNCTION
public.dssmdobjfunc() RETURNS trigger
LANGUAGE plpgsql
AS $$

El dom, 1 oct 2023 a las 15:30, Euler Taveira (<euler@eulerto.com>)
escribió:

On Sat, Sep 30, 2023, at 7:33 AM, Jorge Soro Domenech wrote:

But it show this error:

You didn't show the error message but I suspect it is:

pg_restore: [archiver] unsupported version (1.14) in file header

As you showed the first bytes in the dump file, that first information
(11.18)
is the current Postgres version and the second one (15.2) is the pg_dump
version that you used to create that dump file. Since old pg_dump version
might
not read a new format, you are getting this error. You can fix this issue
using
the pg_restore from version 15.

PS> avoid images; prefer text error messages. It helps search engines to
completely index this message so others can find this discussion.

--
Euler Taveira
EDB https://www.enterprisedb.com/

--

Salutacions,

____________________________

Jorge Soro

I add a more info.

I check .back file and this return "PostreSQL custom database dump -
v1.14-0. Don't understand why the file header have 11.18 database version.

[image: image.png]

El dom, 1 oct 2023 a las 17:28, Jorge Soro Domenech (<jorsodom@gmail.com>)
escribió:

Hello Euler,

thank you for your response.

The backup file has generated external enterprise that me.

You said i try import it backup file with pg_restore version 15, its
correct?

For a correct import, i need the version Postgree database i must have
(11.18) version but i need a pg_restore version 15 for import this "bak
file"

Its possible i have install Postgree database (11.18) and parallel i use
only a pg_restore version 15?

My sistem is a redhat unix.

This is the header backup file.

PGDMP % 6 { a121_prd_md_483100 11.18
15.2 _ 0 0 ENCODING ENCODING SET
client_encoding = 'UTF8';
false ` 0 0
STDSTRINGS
STDSTRINGS ( SET standard_conforming_strings = 'on';
false a 0 0
SEARCHPATH
SEARCHPATH 8 SELECT pg_catalog.set_config('search_path', '',
false);
false b 1262 449003
a121_prd_md_483100 DATABASE CREATE DATABASE a121_prd_md_483100
WITH TEMPLATE = template0 ENCODING = 'UTF8' LOCALE_PROVIDER = libc LOCALE =
'English_United States.1252';
" DROP DATABASE a121_prd_md_483100;
yya121mstrmddb false 2615
2200 public SCHEMA 2 -- *not* creating schema, since initdb
creates it
2 -- *not* dropping schema, since initdb creates it
yya121mstrmddb false ± 1255
449004 dssmdobjfunc() FUNCTION Ê CREATE FUNCTION
public.dssmdobjfunc() RETURNS trigger
LANGUAGE plpgsql
AS $$

El dom, 1 oct 2023 a las 15:30, Euler Taveira (<euler@eulerto.com>)
escribió:

On Sat, Sep 30, 2023, at 7:33 AM, Jorge Soro Domenech wrote:

But it show this error:

You didn't show the error message but I suspect it is:

pg_restore: [archiver] unsupported version (1.14) in file header

As you showed the first bytes in the dump file, that first information
(11.18)
is the current Postgres version and the second one (15.2) is the pg_dump
version that you used to create that dump file. Since old pg_dump version
might
not read a new format, you are getting this error. You can fix this issue
using
the pg_restore from version 15.

PS> avoid images; prefer text error messages. It helps search engines to
completely index this message so others can find this discussion.

--
Euler Taveira
EDB https://www.enterprisedb.com/

--

Salutacions,

____________________________

Jorge Soro

--

Salutacions,

____________________________

Jorge Soro

Jorge Soro Domenech <jorsodom@gmail.com> writes:

I add a more info.
I check .back file and this return "PostreSQL custom database dump -
v1.14-0. Don't understand why the file header have 11.18 database version.

The dump file format version isn't necessarily identical to the
software release version, as we only change the format ID when we
actually change the dump file format. A quick trawl in the source
code says that 1.14 was emitted by pg_dump versions 12.x through 15.x.

regards, tom lane

Thank you, i try it use pg_restore with someone this versions 12.x a 15.x
Thank you

Enviado desde mi iPhone