pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: kehan5800@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19747: pg_dump does not pin array_nulls, so restore mangles NULL array elements
Date: Wed, 07 Oct 2026 08:54:34 +0200
Message-ID: <0d93fce2149eb3512ce665f2706e25a410751c95.camel@cybertec.at> (raw)
In-Reply-To: <1503342.1791317207@sss.pgh.pa.us>
References: <19747-69b01e7fc190cd58@postgresql.org>
	<1201948.1791236086@sss.pgh.pa.us>
	<1503342.1791317207@sss.pgh.pa.us>

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






view thread (5+ messages)  latest in thread

Message-ID: <0d93fce2149eb3512ce665f2706e25a410751c95.camel@cybertec.at>
Permalink:  ../0d93fce2149eb3512ce665f2706e25a410751c95.camel@cybertec.at/
Also on:    postgresql.org/message-id/0d93fce2149eb3512ce665f2706e25a410751c95.camel@cybertec.at

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: laurenz.albe@cybertec.at, tgl@sss.pgh.pa.us, kehan5800@gmail.com
  Subject: Re: BUG #19747: pg_dump does not pin array_nulls, so restore mangles NULL array elements
  In-Reply-To: <0d93fce2149eb3512ce665f2706e25a410751c95.camel@cybertec.at>
  References: <19747-69b01e7fc190cd58@postgresql.org> <1201948.1791236086@sss.pgh.pa.us> <1503342.1791317207@sss.pgh.pa.us> <0d93fce2149eb3512ce665f2706e25a410751c95.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox