Re: PG96 pg_restore connecting to PG95 causes ERROR: unrecognized configuration parameter "idle_in_transaction_session_timeout"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PG96 pg_restore connecting to PG95 causes ERROR: unrecognized configuration parameter "idle_in_transaction_session_timeout"
Date: 2017-05-06 01:14:51
Message-ID: 18643.1494033291@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> When doing a dump+restore upgrade, it's commonly recommended to use the later
> version of pg_restore:

> https://www.postgresql.org/docs/current/static/upgrading.html
> "It is recommended that you use the pg_dump and pg_dumpall programs from the
> newer version of PostgreSQL, to take advantage of enhancements that might have
> been made in these programs. Current releases of the dump programs can read
> data from any server version back to 7.0."

That says to use the pg_dump version *corresponding to the destination
server version*, not the latest version you can find anywhere.

No version of pg_dump has ever promised that its output would load
perfectly cleanly into lower-version destination servers, and that's
not a set of new compatibility constraints that I'd want to take on.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andres Freund 2017-05-06 01:20:55 Re: Logical decoding CPU-bound w/ large number of tables
Previous Message Tom Lane 2017-05-06 00:59:09 Re: Logical decoding CPU-bound w/ large number of tables