Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-bugs-owner+M47123=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
	id 1cmOee-0003r8-GZ
	for pgsql-bugs@arkaria.postgresql.org; Fri, 10 Mar 2017 17:48:40 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-bugs-owner+M47123=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
	id 1cmOed-0006L1-Ui
	for pgsql-bugs@arkaria.postgresql.org; Fri, 10 Mar 2017 17:48:39 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <strk@kbt.io>)
	id 1cmOdt-000505-TH
	for pgsql-bugs@postgresql.org; Fri, 10 Mar 2017 17:47:54 +0000
Received: from relay2-d.mail.gandi.net ([2001:4b98:c:538::194])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <strk@kbt.io>)
	id 1cmOdp-0001XK-VZ
	for pgsql-bugs@postgresql.org; Fri, 10 Mar 2017 17:47:52 +0000
Received: from mfilter23-d.gandi.net (mfilter23-d.gandi.net [217.70.178.151])
	by relay2-d.mail.gandi.net (Postfix) with ESMTP id C4084C5A71;
	Fri, 10 Mar 2017 18:47:46 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter23-d.gandi.net
Received: from relay2-d.mail.gandi.net ([IPv6:::ffff:217.70.183.194])
	by mfilter23-d.gandi.net (mfilter23-d.gandi.net [::ffff:10.0.15.180])
 (amavisd-new, port 10024)
	with ESMTP id O84ppRXH2DaA; Fri, 10 Mar 2017 18:47:45 +0100 (CET)
X-Originating-IP: 46.232.148.34
Received: from localhost (ip-46-232-148-34.static.adsl.cheapnet.it
 [46.232.148.34])
	(Authenticated sender: strk@kbt.io)
	by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id B26CBC5A51;
	Fri, 10 Mar 2017 18:47:44 +0100 (CET)
Date: Fri, 10 Mar 2017 18:47:42 +0100
From: Sandro Santilli <strk@kbt.io>
To: pgsql-bugs@postgresql.org
Subject: Re: BUG #14587: Foreign constraint with newline blows up pg_restore
 catalogue
Message-ID: <20170310174355.GA21663@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <14281.1489163014%40sss.pgh.pa.us>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Pg-Spam-Score: -1.1 (-)
List-Archive: <http://archives.postgresql.org/pgsql-bugs>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-bugs.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@postgresql.org>
List-Post: <mailto:pgsql-bugs@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-bugs>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
X-Mailing-List: pgsql-bugs
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

On 2017-03-10 16:23:34 Tom Lane wrote:
>
> Perhaps this should have been treated as a security issue, but the
> cat's out of the bag now.  I think automated workflows involving -l
> are pretty rare anyway

PostGIS' upgrade procedure [1],[2] is actually based on pg_restore -l,
so maybe it's not so rare: 

[1] http://postgis.net/docs/manual-2.3/postgis_installation.html#hard_upgrade
[2] https://trac.osgeo.org/postgis/browser/tags/2.3.2/utils/postgis_restore.pl.in#L117

--strk; 

  ()   Free GIS & Flash consultant/developer
  /\   https://strk.kbt.io/services.html


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs