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 1uSJFD-0061Xh-0M for pgsql-admin@arkaria.postgresql.org; Thu, 19 Jun 2025 17:40:11 +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 1uSJFA-00DOHm-Op for pgsql-admin@arkaria.postgresql.org; Thu, 19 Jun 2025 17:40:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uSJFA-00DOHe-E1 for pgsql-admin@lists.postgresql.org; Thu, 19 Jun 2025 17:40:09 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uSJF8-002zGT-39 for pgsql-admin@lists.postgresql.org; Thu, 19 Jun 2025 17:40:08 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 48F7E6465B; Thu, 19 Jun 2025 17:40:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elevated-dev.com; s=easymail; t=1750354805; bh=JctyWh+k1nV4hhaQ5sRtfQLs1KzSZB+uWcyIT/d+ezc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=WNuIpVeb8+cQQmYaL0FINKVELlIMFHez2vnHWcjSQ4FssjIpGDSSSmBe85rTfiDS0 3L5zLZtgpSwpMcdKCRuEaDebqhsDq+Teil86Jw7gByBV77SyQ/zoD11Zli0T8lRuit e6a7mbMNfTjG6mV4kgYkGeFW0xX0jjsTkX92rfjhLtpxA0m129Ouk/iuWbMKaf95FO 2F2aU6Xpbo/ScRZkmSo21oRNS752rR1zldu7EQBf2aMNVbCifXZPS0VVsdIaeTupxj dAVqgcnw1A4fM5bRioM7Vc5alrlwD2hstWePcV/KFnt6IcVWebo+DDH9ZIWm0TmKIl JEo5FOrONPjoQ== X-Virus-Scanned: Debian amavisd-new at emo09-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo09-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPY7E58ZfWxJ; Thu, 19 Jun 2025 17:40:05 +0000 (UTC) Received: from smtpclient.apple (165.140.184.195.ip.vcn.com [165.140.184.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id DAE1163E4F; Thu, 19 Jun 2025 17:40:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elevated-dev.com; s=easymail; t=1750354805; bh=JctyWh+k1nV4hhaQ5sRtfQLs1KzSZB+uWcyIT/d+ezc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=WNuIpVeb8+cQQmYaL0FINKVELlIMFHez2vnHWcjSQ4FssjIpGDSSSmBe85rTfiDS0 3L5zLZtgpSwpMcdKCRuEaDebqhsDq+Teil86Jw7gByBV77SyQ/zoD11Zli0T8lRuit e6a7mbMNfTjG6mV4kgYkGeFW0xX0jjsTkX92rfjhLtpxA0m129Ouk/iuWbMKaf95FO 2F2aU6Xpbo/ScRZkmSo21oRNS752rR1zldu7EQBf2aMNVbCifXZPS0VVsdIaeTupxj dAVqgcnw1A4fM5bRioM7Vc5alrlwD2hstWePcV/KFnt6IcVWebo+DDH9ZIWm0TmKIl JEo5FOrONPjoQ== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\)) Subject: Re: update behavior From: Scott Ribe In-Reply-To: Date: Thu, 19 Jun 2025 11:39:54 -0600 Cc: Pgsql-admin Content-Transfer-Encoding: quoted-printable Message-Id: <0D31EA2C-9038-4C2D-A4CD-E602809F16CC@elevated-dev.com> References: <75F792AF-58DF-4559-A2E8-C89060D1E94E@elevated-dev.com> To: "David G. Johnston" X-Mailer: Apple Mail (2.3826.600.51.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Jun 19, 2025, at 11:34=E2=80=AFAM, Scott Ribe = wrote: >=20 >> On Jun 19, 2025, at 11:31=E2=80=AFAM, David G. Johnston = wrote: >>=20 >> Correct. You need a trigger to prevent the update. There is one = provided: suppress_redundant_updates_trigger() >=20 > Or, in my case that prompted this question, I need a WHERE clause for = the ON CONFLICT UPDATE... Wait, should suppress_redundant_updates_trigger be used even in this = case? Would it suppress the update before the constraint checks and = invocation of the ON CONFLICT clause???