MIME-Version: 1.0
From: Sam Kidman <sam@fresho.com>
Date: Wed, 2 Oct 2024 13:23:25 +0800
Message-ID: <CA+FDo=vj+MPhROnDF1b6R=dPrgXeLGUaFbHu=YnHEz7LocSu4A@mail.gmail.com>
Subject: pg_dump 17 produces files incompatible with older server versions
To: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CA%2BFDo%3Dvj%2BMPhROnDF1b6R%3DdPrgXeLGUaFbHu%3DYnHEz7LocSu4A%40mail.gmail.com>
Precedence: bulk

Hello

We're developing a rails application and part of our development
workflow involves dumping out the database schema using pg_dump, which
is restored whenever we drop and create our development database.

As of version 17 we now have SET transaction_timeout = 0 in the schema file.

Unfortunately we use the latest version of the client tools (ie
pg_dump and kin) but we run the same database server version as we use
in production (12) and so now we're unable to import our database
schema with the error below:

ERROR:  unrecognized configuration parameter "transaction_timeout"

It might be easier for us if we could configure pg_dump to _not_
output setting runtime parameters - they're not that important for the
use case of applying a schema to a database for local development.

Are there any other solutions to this issue? It could be quite
troublesome for us as we have a few different postgres server versions
in use in different applications but we use the same set of client
tools for all of them.

Best,

-- 

Sam Kidman

Web Developer

Melbourne

0498 592 582
sam@fresho.com
www.fresho.com