Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l1Ooc-0004nk-F2 for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jan 2021 07:19:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l1Ooa-0008Gw-1G for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Jan 2021 07:19:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l1OoZ-0008Gp-QB for pgsql-hackers@lists.postgresql.org; Mon, 18 Jan 2021 07:19:03 +0000 Received: from dish-sg.nttdocomo.co.jp ([202.19.227.74]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l1OoV-0007Qv-Oy for pgsql-hackers@lists.postgresql.org; Mon, 18 Jan 2021 07:19:02 +0000 X-dD-Source: Outbound Received: from zssg-mailmd104.ddreams.local (zssg-mailmd900.ddreams.local [10.160.172.63]) by zssg-mailou104.ddreams.local (Postfix) with ESMTP id 80065120117; Mon, 18 Jan 2021 16:18:55 +0900 (JST) Received: from t113sg-mailcc12.ddreams.local (t113sg-mailcc12.ddreams.local [100.66.13.87]) by zssg-mailmd104.ddreams.local (dDREAMS) with ESMTP id <0QN401D3ECBJI770@dDREAMS>; Mon, 18 Jan 2021 16:18:55 +0900 (JST) Received: from t113sg-mailcc12 (localhost [127.0.0.1]) by t113sg-mailcc12.ddreams.local (unknown) with SMTP id 10I7It9X000903; Mon, 18 Jan 2021 16:18:55 +0900 Received: from zssg-mailmf103.ddreams.local (unknown [127.0.0.1]) by zssg-mailmf103.ddreams.local (Postfix) with ESMTP id ABAC07E603C; Mon, 18 Jan 2021 16:18:38 +0900 (JST) Received: from zssg-mailmf103.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A9DD78E6070; Mon, 18 Jan 2021 16:18:38 +0900 (JST) Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id A7F478E605C; Mon, 18 Jan 2021 16:18:38 +0900 (JST) X-IMSS-HAND-OFF-DIRECTIVE: localhost:10026 Received: from zssg-mailmf103.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B64E28E605A; Mon, 18 Jan 2021 16:18:37 +0900 (JST) Received: from zssg-mailua102.ddreams.local (unknown [10.160.172.62]) by zssg-mailmf103.ddreams.local (Postfix) with ESMTP; Mon, 18 Jan 2021 16:18:37 +0900 (JST) Received: from [10.132.152.55] (unknown [10.160.179.1]) by zssg-mailua102.ddreams.local (dDREAMS) with ESMTPA id <0QN400Q4CCAW8TC0@dDREAMS>; Mon, 18 Jan 2021 16:18:32 +0900 (JST) Subject: Re: list of extended statistics on psql References: <20210107144713.GA8872@alvherre.pgsql> <61cba5af-5a58-6bda-610c-420077b780c3@enterprisedb.com> <1045d2cb-7ecd-e6bf-cb50-8eeea89cc4b0@nttcom.co.jp_1> <9e76ce7a-e7ab-5f08-9938-59fffc20d106@enterprisedb.com> <29e16ceb-8777-4297-19c8-245242dd7473@enterprisedb.com> <876efa7e-2067-a4f9-d7e8-f6025440c870@nttcom.co.jp_1> <0e84aa72-25f2-1849-753f-f827949132b3@enterprisedb.com> <85e7e1e7-c2f0-a4a0-61de-6e7ecaee44e3@nttcom.co.jp_1> <79d3a4c5-1efe-5b9e-c06e-3a907b531013@nttcom.co.jp_1> <20210115084741.GA91293@nol> From: Tatsuro Yamada Message-id: <809a4d20-edcd-9c0f-c91f-aef13458cefd@nttcom.co.jp_1> Date: Mon, 18 Jan 2021 16:18:32 +0900 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-version: 1.0 In-reply-to: <20210115084741.GA91293@nol> Content-type: text/plain; charset=utf-8; format=flowed Content-language: en-US Content-transfer-encoding: 7bit X-TM-AS-GCONF: 00 To: Julien Rouhaud Cc: Tomas Vondra , Alvaro Herrera , Tomas Vondra , Michael Paquier , Pavel Stehule , PostgreSQL Hackers X-CC-Mail-RelayStamp: CC/Mail Relayed List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi Julien, On 2021/01/15 17:47, Julien Rouhaud wrote: > Hello Yamada-san, > > I reviewed the patch and don't have specific complaints, it all looks good! > > I'm however thinking about the "requested" status. I'm wondering if it could > lead to people think that an ANALYZE is scheduled and will happen soon. > Maybe "defined" or "declared" might be less misleading, or even "waiting for > analyze"? Thanks for reviewing the patch. Yeah, "waiting for analyze" was preferable but it was a little long to use on the columns. Unfortunately, I couldn't imagine a suitable term. Therefore, I'm keeping it as is. Regards, Tatsuro Yamada