Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rMnj3-006k62-QU for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jan 2024 11:23:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rMnj2-004LiX-7H for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jan 2024 11:23:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rMnj1-004Lgg-0K for pgsql-hackers@lists.postgresql.org; Mon, 08 Jan 2024 11:23:23 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rMnix-000TJO-KA for pgsql-hackers@lists.postgresql.org; Mon, 08 Jan 2024 11:23:21 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 733E1320126F; Mon, 8 Jan 2024 06:23:17 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Mon, 08 Jan 2024 06:23:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1704712996; x= 1704799396; bh=NeZ6Shx/3sIB5yT7mr4sM8JwBq+otvnnNighCR1aWE0=; b=U jpO6FsIGBxnRaUk6Xr/g72mmpxgVQfIZkij6BkO9r+tA39vo712du7MUhAJwVWj4 SLe9rz4dXYL7mKBOcr7wOyN3ml7jn6miEB4MNu/6lWGvwk1jHFTUsr09nQPksAnE y7cIssCKOZNBiGKsrWMOqoOIMIGB3wdeJjECI156BtwQlU7lBLvgF75qvd2wMRws BGJx40MJd82oZz4gNlwm9iy2YnuIpiTgfsDHozhmdidlnhbydTzUFRI2kL7gaw5D XQAfOePDSIttqdMnmkwEVbYczf/cD/PEmxA8jkM51UrH7D1uvtClSOzUyHettmwZ u+6XeOQR3PGOMLaCpXlcA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdehjedgvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 8 Jan 2024 06:23:16 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1704712994; bh=8JRcX7NiHHO/fBPqZbLoeVd85H8OupstRsQQSQbIbhA=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=FqZ2GIq7AS7YrMplWgUK2/Ag6Wzvb7NaJLe8Djl8EI8Og8saJuo8KPuFDvSPPyNdG 8rRb9EtPfO9p3qeALFna2Odie/0AIF0C04h7yZTbLZu0W8VlSY3yjr2+vcctzXIdY9 10wUeoiMFTIFWJKZi1sDJfOLXMMp3bWrtIGoMoPHgwJ14cIiIomlmVT8iUWw8QbJUG F7RJEY9GTRXNCWpCZtNup1KtsvDzgpw22DG+bUI4tvsvkj1dOL+aEh44auk0VSBX01 QfyL4ownO+kqrtl7lsABc7LvHP9w7x2M/JL6FNS5cIYN4sR/05A3QtOw10I9FIzJON 9mL6/ZueyqpjQ== Received: by schmee.alvh.no-ip.org (Postfix, from userid 1000) id 961D29D; Mon, 8 Jan 2024 12:23:14 +0100 (CET) Date: Mon, 8 Jan 2024 12:23:14 +0100 From: Alvaro Herrera To: James Wang Cc: pgsql-hackers@lists.postgresql.org Subject: Re: brininsert optimization opportunity Message-ID: <202401081123.3qqe5qokxyo2@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <170315311175.2631681.12214566971840476644.pgcf@coridan.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Dec-21, James Wang wrote: > Hi All, not sure how to "Specify thread msgid" - choose one which i think is close to my new feature request. Hello James, based on the "Specify thread msgid" message it looks like you were trying to request a feature using the Commitfest website? That won't work; the commitfest website is only intended as a tracker of in-progress development work. Without a Postgres code patch, that website doesn't help you any. What you have done amounts to hijacking an unrelated mailing list thread, which is discouraged and frowned upon. That said, sadly we don't have any official feature request system, Please start a new thread by composing an entirely new message to pgsql-hackers@lists.postgresql.org, and don't use the commitfest website for it. That said, > query: > > SELECT count(1) FROM table1 t1 JOIN table2 t2 ON t1.id = t2.id WHERE t1.a_indexed_col='some_value' OR t2.a_indexed_col='some_vable'; > > can the server automatically replace the OR logic above with UNION please? i.e. replace it with: > > (SELECT count(1) FROM table1 t1 JOIN table2 t2 ON t1.id = t2.id WHERE t1.a_indexed_col='some_value' ) > UNION > (SELECT count(1) FROM table1 t1 JOIN table2 t2 ON t1.id = t2.id WHERE t2.a_indexed_col='some_vable'); I have the feeling that this has already been discussed, but I can't find anything useful in the mailing list archives. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Saca el libro que tu religión considere como el indicado para encontrar la oración que traiga paz a tu alma. Luego rebootea el computador y ve si funciona" (Carlos Duclós)