public inbox for [email protected]
help / color / mirror / Atom feedFrom: Corey Huinker <[email protected]>
To: Matthias van de Meent <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: SQL-level pg_datum_image_equal
Date: Sat, 20 Dec 2025 11:07:11 -0500
Message-ID: <CADkLM=e_fWhLdwE=HnExSCO6bY2WVpaUMbQRSBN2nw6fh78qUg@mail.gmail.com> (raw)
In-Reply-To: <CAEze2WhsqYjg0oGY+7yooimUK7zRc9PY9u8u-Oo=VmJ+DAAkKg@mail.gmail.com>
References: <CAEze2WhsqYjg0oGY+7yooimUK7zRc9PY9u8u-Oo=VmJ+DAAkKg@mail.gmail.com>
On Wed, Dec 10, 2025 at 12:46 PM Matthias van de Meent <
[email protected]> wrote:
> Hi,
>
> One of our customers has this workload where every so often they
> update the whole table to make sure it's up-to-date. In general, you'd
> probably want to use MERGE for such a workload and ignore all rows
> that already have only matching data, but there's a catch: PostgreSQL
> doesn't have an efficient way to check if the provided data is
> actually equal in all senses of the word, so we can't easily and
> cheaply determine whether an update is needed; which is one reason why
> the full table was updated every time.
>
Have you ruled out the suppress_redundant_updates_trigger?
https://www.postgresql.org/docs/current/functions-trigger.html
view thread (11+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: SQL-level pg_datum_image_equal
In-Reply-To: <CADkLM=e_fWhLdwE=HnExSCO6bY2WVpaUMbQRSBN2nw6fh78qUg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox