Re: pg_dump truncating queries in error messages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump truncating queries in error messages
Date: 2017-03-26 20:09:38
Message-ID: 15187.1490558978@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Shaplov 2017-03-26 20:23:10 Re: [PATCH] Move all am-related reloption code into src/backend/access/[am-name] and get rid of relopt_kind for custom AM
Previous Message Thomas Munro 2017-03-26 19:38:01 Re: [sqlsmith] Unpinning error in parallel worker