Thread: pg_dump truncating queries in error messages
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
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
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