From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
cc: Nathan Bossart <nathandbossart@gmail.com>,
        Corey Huinker <corey.huinker@gmail.com>,
        Fujii Masao <masao.fujii@oss.nttdata.com>,
        Robert Haas <robertmhaas@gmail.com>,
        Peter Eisentraut <peter@eisentraut.org>,
        pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: pg_dump --with-* options
In-reply-to: <98be6ad839968cc9551161d14bc2d6ba4eadb2b9.camel@j-davis.com>
References: <7cc52488-f876-4ad3-affd-6e4b0ef0cb09@eisentraut.org>
 <aEMLzPQtjRbj2R7X@nathan>
 <CA+TgmoactJEUHeXuxHLKNXHzm6-XrQFigPur-4nHTMFSiSRkiQ@mail.gmail.com>
 <aErpuM6RXSlK1FBW@nathan>
 <1854ffbf-f8eb-4bc3-b9f8-223bbf58c392@oss.nttdata.com>
 <271f899c54d112b353e009286af7c6cdb7c3d609.camel@j-davis.com>
 <aEyK6FxJqcv53s8b@nathan>
 <94f89b0a-5d83-4a67-9092-50ba3913441c@oss.nttdata.com>
 <CADkLM=fXSiX4GQ7F6__z+ofGpp0QwwytGP-GNeVQyMhc29bbwQ@mail.gmail.com>
 <aFCIB1AwXuNzxHXX@nathan>
 <98be6ad839968cc9551161d14bc2d6ba4eadb2b9.camel@j-davis.com>
Comments: In-reply-to Jeff Davis <pgsql@j-davis.com>
	message dated "Mon, 16 Jun 2025 15:57:16 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <689259.1750115357.1@sss.pgh.pa.us>
Date: Mon, 16 Jun 2025 19:09:17 -0400
Message-ID: <689260.1750115357@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/689260.1750115357%40sss.pgh.pa.us>
Precedence: bulk

Jeff Davis <pgsql@j-davis.com> writes:
> Does it make any sense to be off by default in 18 and on in some later
> release?

Probably not, especially if part of the argument for on-by-default
is to allow simplification of the switch set.  We don't get that
benefit if we ship with off-by-default, and we won't be able to
get it later.

I find myself increasingly persuaded by Corey's point of view ...

			regards, tom lane