Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fftdx-0001Ei-B1 for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Jul 2018 21:05:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fftdv-0004y7-Md for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Jul 2018 21:05:51 +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.89) (envelope-from ) id 1fftdv-0004y0-5b for pgsql-hackers@lists.postgresql.org; Wed, 18 Jul 2018 21:05:51 +0000 Received: from mail-qk0-x241.google.com ([2607:f8b0:400d:c09::241]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fftdr-0007gN-Uw for pgsql-hackers@lists.postgresql.org; Wed, 18 Jul 2018 21:05:49 +0000 Received: by mail-qk0-x241.google.com with SMTP id 26-v6so3167188qks.9 for ; Wed, 18 Jul 2018 14:05:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=L2v0In2nJ6YnryEg6baMcl2VW/YynHWFUaq5HRQPGt8=; b=ajehjNPfhekTjjDD1EsgXeKDn3og4hZ+zSw9gwI54TDo6uBW7Aemu/1oTgCfoWu2ug vxQM8nxMPQ0XYP4/j+ryBVDIC1eWCh/f328Pal2CzED3jc+5KVDzLqH2S5wMPEotjWWq JF5jV+BlNaESGTjHXcPgBlT5BytZq/NjcU8Vn7/dUuSpXtM15WrKxHaAWAO7X5olnpJu 7UdieYD5c+z+vZ5u60Bv30hBqcYBsOm58K2Cgrdmog0i4l2QtB4f7SqwDfxqc4dU0U5I QqhJvbJ+TlNhvnZevsGuIcqnIaCTZnoVMjFoW666pBrAvj1CtDM2kRT6nn8KDbdWm9yV J8XA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=L2v0In2nJ6YnryEg6baMcl2VW/YynHWFUaq5HRQPGt8=; b=HTfvm+fEEoKI/CpFnQvRwCloP9WvP1f9u/tWnrlt0ctERZ2xx3P1y2qGJafki6BKSf 21H4ZEVh3pTGaqexFUnPyyB2poTM9DwfElUG+84ys1EhHal1dzHSVzT5K6Lf1+oJ5jHT PrvHeCeBc2kHFEgweLZy/d41AeaXt7Is+6q5hL1wdBzK0gdvlKFN5r66kt9Z6W9KTzrO /oUFYOav8r+82GaBm5+6QwGjIwYnrcrRXT3ET3rMN7u7JYo/jzMmB9mUIw0w8b8W7t7+ uzmvYEPX5dyqxxmFyS81/KTVDXF8UQwhef6PhHl+BD5FWSwD45m63+MQ1NDatFD225nv NXrw== X-Gm-Message-State: AOUpUlGiSMuW1k/kpnUnpQbMp2zVey9LNhJ8ZZwb+bQ8dxP9Indmz7xx i4hP28Clm5mHjoXlI79b6olgJg== X-Google-Smtp-Source: AAOMgpfIyGgaBiumxD/64Ru4cPip4YuUP2bkQBZ2x7nkkfjhEqJ0/EZRaAujNIG/FGhUuthPAZqLgw== X-Received: by 2002:a37:8b47:: with SMTP id n68-v6mr6880049qkd.27.1531947946865; Wed, 18 Jul 2018 14:05:46 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([179.56.48.71]) by smtp.gmail.com with ESMTPSA id o25-v6sm2178127qtp.87.2018.07.18.14.05.46 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 18 Jul 2018 14:05:46 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 990CFCCB; Wed, 18 Jul 2018 17:05:44 -0400 (-04) Date: Wed, 18 Jul 2018 17:05:44 -0400 From: Alvaro Herrera To: Tom Lane Cc: "David G. Johnston" , PostgreSQL Hackers Subject: Re: psql's \d versus included-index-column feature Message-ID: <20180718210544.ynej3c6oos45u5t7@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <24241.1531946776@sss.pgh.pa.us> User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2018-Jul-18, Tom Lane wrote: > I can sympathize with the eyestrain argument against t/f, but the > above doesn't seem like an improvement --- in particular, "Data" > as the column header seems quite content-free. My counterproposal > is to keep "Key" as the header and use "Yes"/"No" as the values. I think "Key: no" is a bit obscure -- using "included" is a bit more self-documenting and lends better to documentation searches. > I'd be OK with "Key"/"Included" as the values if someone can > propose an on-point column header to go with those. "Role"? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services