| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump truncating queries in error messages |
| Date: | 2017-03-29 19:21:54 |
| Message-ID: | c5ea7fe7-355d-3f71-bbd9-a8a21c4ab86c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/26/17 16:09, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-03-29 19:27:15 | PG_GETARG_GISTENTRY? |
| Previous Message | Andres Freund | 2017-03-29 19:10:12 | Re: Schedule and Release Management Team for PG10 |