Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6Yjg-0003rT-8V for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 10:46:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6Yje-0006sE-VI for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Mar 2019 10:46:14 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6Yje-0006s7-Np for pgsql-hackers@lists.postgresql.org; Wed, 20 Mar 2019 10:46:14 +0000 Received: from mail.thelabyrinth.net ([45.56.70.56]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6Yjc-0003IE-JV for pgsql-hackers@postgresql.org; Wed, 20 Mar 2019 10:46:14 +0000 Received: from Davids-MacBook.local (unknown [41.136.236.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: dsteele) by mail.thelabyrinth.net (Postfix) with ESMTPSA id 74FA15468B; Wed, 20 Mar 2019 10:46:09 +0000 (UTC) Subject: Re: Re: query logging of prepared statements To: Justin Pryzby Cc: Arthur Zakirov , pgsql-hackers@postgresql.org References: <20190208132953.GF29720@telsasoft.com> <20190215145704.GW30291@telsasoft.com> <20190227180653.GF28750@telsasoft.com> <70868e0d-2a29-36c8-e3e2-f54a56804bc4@postgrespro.ru> <20190304183150.GK29584@telsasoft.com> <345f3504-e3cd-3a01-c593-ebbbe555dd69@postgrespro.ru> From: David Steele Message-ID: <2da70a91-2a22-9d78-84ba-cba4b71c7541@pgmasters.net> Date: Wed, 20 Mar 2019 14:46:00 +0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: <345f3504-e3cd-3a01-c593-ebbbe555dd69@postgrespro.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi Justin, On 3/5/19 2:30 PM, Arthur Zakirov wrote: > On 04.03.2019 21:31, Justin Pryzby wrote: >> It wasn't intentional.  Find attached v3 patch which handles that case, >> by removing the 2nd call to errdetail_execute() ; since it's otherwise >> unused, >> so remove that function entirely. > > Thank you. > >> Thanks for reviewing.  I'm also interested in discussion about whether >> this >> change is undesirable for someone else for some reason ?  For me, the >> existing >> output seems duplicative and "denormalized".  :) > > I perfectly understand your use case. I agree, it is duplicated. But I > think some people may want to see it at every EXECUTE, if they don't > want to grep for the prepared statement body which was logged earlier. > > I think it would be good to give possibility to configure this behavior. > At first version of your patch you relied on log_error_verbosity GUC. > I'm not sure that this variables is suitable for configuring visibility > of prepared statement body in logs, because it sets more general > behavior. Maybe it would be better to introduce some new GUC variable if > the community don't mind. Thoughts on this? Regards, -- -David david@pgmasters.net