From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: pg_dump truncating queries in error messages
Date: Wed, 29 Mar 2017 15:21:54 -0400
Message-ID: <c5ea7fe7-355d-3f71-bbd9-a8a21c4ab86c@2ndquadrant.com> (raw)
In-Reply-To: <15187.1490558978@sss.pgh.pa.us>
References: <63201ef9-26fb-3f1f-664d-98531678cebc@2ndquadrant.com>
<15187.1490558978@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 3/26/17 16:09, Tom Lane wrote:
> 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.
OK done.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us
Subject: Re: pg_dump truncating queries in error messages
In-Reply-To: <c5ea7fe7-355d-3f71-bbd9-a8a21c4ab86c@2ndquadrant.com>
* 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