On Tue, 2026-10-06 at 16:06 -0400, Tom Lane wrote:
> I wrote:
> > PG Bug reporting form <noreply@postgresql.org> writes:
> > > [misbehavior with array_nulls on]
>
> > Meh. TBH, that GUC was past its shelf life ten years ago. What
> > I'd rather do about this report is just summarily remove the GUC.
> > If we make pg_dump issue a SET for it then we'll never be able
> > to remove it.
>
> Concretely, about like this. (BTW, another argument for doing
> this rather than fixing pg_dump is that there are a ton of other
> applications that will likely misbehave if array_nulls is turned
> on underneath them.)
+1
I have never seen this used in the field. One less potential headache!
Yours,
Laurenz Albe
