Jeff Davis <pgsql@j-davis.com> writes:
> On Sat, 2025-03-01 at 13:52 -0500, Greg Sabino Mullane wrote:
>> Also, anything trained to parse pg_dump output will have to learn
>> about the new SELECT pg_restore_ calls with their multi-line formats
>> (not 100% sure we don't have that anywhere, as things like "SELECT
>> setval" and "SELECT set_config" are single line, but there may be
>> existing things)
> That's an interesting point. What tools are currrently trying to parse
> pg_dump output?
That particular argument needs to be rejected vociferously. Otherwise
we could never make any change at all in what pg_dump emits. I think
the standard has to be "if you parse pg_dump output, it's on you to
cope with any legal SQL".
I do grasp Greg's larger point that this is a big change in pg_dump's
behavior and will certainly break some expectations. I kind of lean
to the position that we'll be sad in the long run if we don't change
the default, though. What other part of pg_dump's output is not
produced by default?
regards, tom lane
