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 1nWR3Y-0005QB-Vi for pgsql-bugs@arkaria.postgresql.org; Mon, 21 Mar 2022 23:03:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nWR3X-0000Y5-T4 for pgsql-bugs@arkaria.postgresql.org; Mon, 21 Mar 2022 23:03:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWR3X-0000XG-Kg for pgsql-bugs@lists.postgresql.org; Mon, 21 Mar 2022 23:03:19 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWR3V-0007xi-EF for pgsql-bugs@lists.postgresql.org; Mon, 21 Mar 2022 23:03:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 22LN3FJE2409083; Mon, 21 Mar 2022 19:03:15 -0400 From: Tom Lane To: Peter Geoghegan cc: yaser.amiri95@gmail.com, PostgreSQL mailing lists Subject: Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded In-reply-to: References: <17445-fb74db6348391e85@postgresql.org> <2405214.1647901437@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Mon, 21 Mar 2022 15:53:12 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2409081.1647903795.1@sss.pgh.pa.us> Date: Mon, 21 Mar 2022 19:03:15 -0400 Message-ID: <2409082.1647903795@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Geoghegan writes: > That being said, I *don't* think that it makes sense to support > paramaters in conflict_target's WHERE clause -- that should be static, > not dynamic. ISTM that it would be somewhat useful to have that case > throw an error, in an immediate and obvious way, with an accompanying > HINT. Hm. I don't have an opinion on whether this'd be a useful case to support, but I agree that actually doing so is not terribly feasible. Perhaps a specific error message would be worth the trouble. regards, tom lane