pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_dump truncating queries in error messages
3+ messages / 2 participants
[nested] [flat]
* pg_dump truncating queries in error messages
@ 2017-03-26 19:26 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-03-26 20:09 ` Re: pg_dump truncating queries in error messages Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: Peter Eisentraut @ 2017-03-26 19:26 UTC (permalink / raw)
To: pgsql-hackers
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.
--
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pg_dump truncating queries in error messages
2017-03-26 19:26 pg_dump truncating queries in error messages Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
@ 2017-03-26 20:09 ` Tom Lane <tgl@sss.pgh.pa.us>
2017-03-29 19:21 ` Re: pg_dump truncating queries in error messages Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2017-03-26 20:09 UTC (permalink / raw)
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; +Cc: pgsql-hackers
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pg_dump truncating queries in error messages
2017-03-26 19:26 pg_dump truncating queries in error messages Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-03-26 20:09 ` Re: pg_dump truncating queries in error messages Tom Lane <tgl@sss.pgh.pa.us>
@ 2017-03-29 19:21 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 0 replies; 3+ messages in thread
From: Peter Eisentraut @ 2017-03-29 19:21 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2017-03-29 19:21 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-03-26 19:26 pg_dump truncating queries in error messages Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-03-26 20:09 ` Tom Lane <tgl@sss.pgh.pa.us>
2017-03-29 19:21 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
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