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 1hx9cp-0008Na-U4 for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Aug 2019 12:40:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hx9co-0001OR-EW for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Aug 2019 12:40:34 +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 1hx9co-0001Iy-40 for pgsql-hackers@lists.postgresql.org; Mon, 12 Aug 2019 12:40:34 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hx9cg-0000uW-UP for pgsql-hackers@postgresql.org; Mon, 12 Aug 2019 12:40:33 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id B28121643D7EC for ; Mon, 12 Aug 2019 05:40:24 -0700 (MST) Date: Mon, 12 Aug 2019 05:40:24 -0700 (MST) From: Jim Finnerty To: pgsql-hackers@postgresql.org Message-ID: <1565613624729-0.post@n3.nabble.com> In-Reply-To: References: <1553110765067-0.post@n3.nabble.com> <1553116679891-0.post@n3.nabble.com> <1553117433667-0.post@n3.nabble.com> <1553120398016-0.post@n3.nabble.com> <20190409212613.udbyn2ezioz2clwn@momjian.us> <1565400424579-0.post@n3.nabble.com> Subject: Re: [survey] New "Stable" QueryId based on normalized query text MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk If hashing names instead of using OIDs is too expensive for some workload, then that workload would need to be able to turn statement hashing off. So it needs to be optional, just like queryId is optionally computed today. For many cases the extra overhead of hashing object names is small compared to optimization time plus execution time. ----- Jim Finnerty, AWS, Amazon Aurora PostgreSQL -- Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html