Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ctJAO-0000Ty-Q7 for pgsql-hackers@arkaria.postgresql.org; Wed, 29 Mar 2017 19:22:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ctJAO-0004T3-CO for pgsql-hackers@arkaria.postgresql.org; Wed, 29 Mar 2017 19:22:00 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ctJAM-0004MX-Gb for pgsql-hackers@postgresql.org; Wed, 29 Mar 2017 19:21:58 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ctJAK-0000fo-96 for pgsql-hackers@postgresql.org; Wed, 29 Mar 2017 19:21:57 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2B97821982; Wed, 29 Mar 2017 15:21:55 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 29 Mar 2017 15:21:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=etQTird9VrJuw62AHnDeU7eQciJbDx2jr8fNWmFGNxQ=; b=NdvHNKJE w+0+i+fzoi/fGM/zjzBgOQuuJptgZhqundaPBpzka3vVIwhRKROPTxe2bzT0naEm B13aUUEv/BCIoypacge96RYl7VlBKznb4h5KQn2dPXJKzYfaaYCHvSNDYktmONF1 dQxDCdEyxoc6rKME2nC5m7Pvky4gb+K1XLqX4UlT5e9WeOP+O+Hkgt9MHlMiuuiv z2UY/k4P8WmBsxGpOvuYB29eXPUMUkPXfQhxnCIih2HJLf09wzu7vDMkKsZ7cGMh TGlL4Wvx5MVnHp0QpnBGJawbjJB/niSxQJSLkpuy274WiL8T27C3fVCnCC5sa7fA m9LVjowY52cR3w== X-ME-Sender: X-Sasl-enc: MFStW6IHZ6lx0B8TuaUK6duRPUS0GU5ewWe5nx07+Jml 1490815315 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id DB04F7E46B; Wed, 29 Mar 2017 15:21:54 -0400 (EDT) Subject: Re: pg_dump truncating queries in error messages To: Tom Lane References: <63201ef9-26fb-3f1f-664d-98531678cebc@2ndquadrant.com> <15187.1490558978@sss.pgh.pa.us> Cc: pgsql-hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 29 Mar 2017 15:21:54 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <15187.1490558978@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 3/26/17 16:09, Tom Lane wrote: > Peter Eisentraut 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