Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Zwv7K-0006yi-5W for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Nov 2015 16:52:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1Zwv7J-0000Yc-Nd for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Nov 2015 16:52:57 +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) (envelope-from ) id 1Zwv61-0007Ws-9y for pgsql-hackers@postgresql.org; Thu, 12 Nov 2015 16:51:37 +0000 Received: from fr1.2ndquadrant.fr ([94.23.17.124]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1Zwv5x-0005up-Rv for pgsql-hackers@postgresql.org; Thu, 12 Nov 2015 16:51:35 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by fr1.2ndquadrant.fr (Postfix) with ESMTP id 5B8987D991; Thu, 12 Nov 2015 17:51:31 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at fr1.2ndquadrant.fr Received: from fr1.2ndquadrant.fr ([127.0.0.1]) by localhost (fr1.2ndquadrant.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jFRZZST6V79k; Thu, 12 Nov 2015 17:51:29 +0100 (CET) Received: from [192.168.0.3] (ath91-3-88-167-161-184.fbx.proxad.net [88.167.161.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: charles) by fr1.2ndquadrant.fr (Postfix) with ESMTPSA id 39C187D95E; Thu, 12 Nov 2015 17:51:29 +0100 (CET) Subject: Re: psql: add \pset true/false To: Matthijs van der Vleuten , Brendan Jurd References: <0949c317-3ec4-4516-a3aa-33a6cfbf5267@mm> <5631FCAF.9060204@joh.to> <27336.1446126627@sss.pgh.pa.us> Cc: Tom Lane , Marko Tiikkaja , Daniel Verite , PostgreSQL hackers From: Vik Fearing Message-ID: <5644C390.6040804@2ndquadrant.fr> Date: Thu, 12 Nov 2015 17:51:28 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.3 (--) 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 11/12/2015 05:41 PM, Matthijs van der Vleuten wrote: > >> On 12 Nov 2015, at 14:21, Brendan Jurd wrote: >> >> On Fri, 30 Oct 2015 at 00:51 Tom Lane > wrote: >> The really key argument that hasn't been addressed here is why does such >> a behavior belong in psql, rather than elsewhere? Surely legibility >> problems aren't unique to psql users. Moreover, there are exactly >> parallel facilities for other datatypes on the server side: think >> DateStyle or bytea_output. So if you were trying to follow precedent >> rather than invent a kluge, you'd have submitted a patch to create a GUC >> that changes the output of boolout(). >> >> I find Tom's analogy to datestyle and bytea_output convincing. >> >> +1 for a GUC that changes the behaviour of boolout. > > -1 for changing boolout(). It will break anything that receives boolean values from the server. How a client is going to display values (of any type) is logic that should belong in the client, not in the protocol. I fully agree. This is something I feel should happen in the client. -- Vik Fearing +33 6 46 75 15 36 http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers