Re: Downgrade pgsql 17 to pgsql 12 question - Mailing list pgsql-general

From Tom Lane
Subject Re: Downgrade pgsql 17 to pgsql 12 question
Date
Msg-id 4089348.1758905461@sss.pgh.pa.us
Whole thread Raw
In response to Downgrade pgsql 17 to pgsql 12 question  (Ashish Mukherjee <ashish.mukherjee@gmail.com>)
List pgsql-general
Ashish Mukherjee <ashish.mukherjee@gmail.com> writes:
> When I do dump/restore like this for a test table, I get the following
> errors during restore but the table gets restored fine.

> pg_restore: error: while PROCESSING TOC:
>  error: pg_restore:  error:   pg_restore:  from TOC entry 17168; 1259
> 58572315 TABLE pkgs s14
> pg_restore: error: pg_restore: pg_restore: pg_restore:   from TOC entry
> 17168; 1259 58572315 TABLE pkgs s14
> pg_restore:   error: pg_restore: from TOC entry 17168; 1259 58572315 TABLE
> pkgs s14
> pg_restore: error: pg_restore: from TOC entry 17168; 1259 58572315 TABLE
> pkgs s14
> error: from TOC entry 17168; 1259 58572315 TABLE pkgs s14
> pg_restore: warning: errors ignored on restore: 2

FWIW, the only output I see when trying a simple restore of a couple
of tables from HEAD into a v12 server is

pg_restore: error: could not execute query: ERROR:  unrecognized configuration parameter "transaction_timeout"
Command was: SET transaction_timeout = 0;
pg_restore: warning: errors ignored on restore: 1

which is expected since v12 didn't have transaction_timeout.
(If you use parallel mode you will see this error per-worker.)

This means you can't use --single-transaction, but it should
work otherwise as long as you're not using DDL features v12
didn't have.

So I'm wondering why your output doesn't show that, and also
why it fails to show the text of whatever error you are getting.
Can you make a reproducible test case that behaves like that?

            regards, tom lane



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Downgrade pgsql 17 to pgsql 12 question
Next
From: veem v
Date:
Subject: Re: Correct query for monitor