Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-hackers-owner+M322393=pgsql-hackers-arkari@postgresql.org>)
	id 1csETx-0005Y3-V8
	for pgsql-hackers@arkaria.postgresql.org; Sun, 26 Mar 2017 20:09:46 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-hackers-owner+M322393=pgsql-hackers-arkari@postgresql.org>)
	id 1csETx-0004ds-GQ
	for pgsql-hackers@arkaria.postgresql.org; Sun, 26 Mar 2017 20:09:45 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1csETv-0004bU-D4
	for pgsql-hackers@postgresql.org; Sun, 26 Mar 2017 20:09:43 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1csETs-0007Fk-Va
	for pgsql-hackers@postgresql.org; Sun, 26 Mar 2017 20:09:42 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v2QK9c4H015188;
	Sun, 26 Mar 2017 16:09:38 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: pg_dump truncating queries in error messages
In-reply-to: <63201ef9-26fb-3f1f-664d-98531678cebc@2ndquadrant.com>
References: <63201ef9-26fb-3f1f-664d-98531678cebc@2ndquadrant.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
	message dated "Sun, 26 Mar 2017 15:26:23 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15186.1490558978.1@sss.pgh.pa.us>
Date: Sun, 26 Mar 2017 16:09:38 -0400
Message-ID: <15187.1490558978@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> When reporting an error from a query, pg_dump truncates the reported
> query to 128 characters (pg_backup_db.c ExecuteSqlCommand()).

> Is this (still) sensible?  The kind of queries that pg_dump is running
> nowadays, I find myself unable to debug them if they are truncated at
> that length.

Not clear that it ever was very sensible ... +1 for removing the limit.

			regards, tom lane


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