Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1csDo7-0002rT-UW for pgsql-hackers@arkaria.postgresql.org; Sun, 26 Mar 2017 19:26:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1csDo7-0002TS-9w for pgsql-hackers@arkaria.postgresql.org; Sun, 26 Mar 2017 19:26:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1csDo5-0002Qy-41 for pgsql-hackers@postgresql.org; Sun, 26 Mar 2017 19:26:29 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1csDo1-0006TN-Qq for pgsql-hackers@postgresql.org; Sun, 26 Mar 2017 19:26:28 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 934A820B44 for ; Sun, 26 Mar 2017 15:26:24 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Sun, 26 Mar 2017 15:26:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=fR6+rdFopwcRHBczSj Aa0tnAErdijdWreHgNvG2Q+Hw=; b=ARySzZk+3w0q6ADiEbK0hltyZ28B259Uq3 NMPuE8Y9dB1lXJaEkhDzaIfWnj20tTRk+I1gXVmIwgGK7Ug7Ya9/uYB/5ygQ5S7r Q1fFA8T/nWrDgwWk8d5yilGBCbxKV8grHNLFzQbB7fKX32HOYzAfLU8eugH7NNa/ DnXKSg9JZfbQPYMLRbcYyGMRjVq7HT/3MK2cfy6PThRwmQvArZv726SGNpGLurT0 ZlvOAEfDnCqwBC+AsfZUnyFMBGoJmzCznpjrW/BuQO8rMqZGnJ6Jt3MzU2v1a6Mz EqYnG3R8gsrlPiXi0gYC3Xoqq7RBUDwRixopwDHS6ns4ArlWnFHQ== X-ME-Sender: X-Sasl-enc: v2hJC4RTme4yQOfvteWbtk7cKctPk/m1tx7JNMOF9Ahg 1490556384 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 3241E24519 for ; Sun, 26 Mar 2017 15:26:24 -0400 (EDT) To: pgsql-hackers From: Peter Eisentraut Subject: pg_dump truncating queries in error messages Organization: 2ndQuadrant Message-ID: <63201ef9-26fb-3f1f-664d-98531678cebc@2ndquadrant.com> Date: Sun, 26 Mar 2017 15:26:23 -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 Content-Type: text/plain; charset=utf-8 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 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