Re: SQL-level pg_datum_image_equal
Corey Huinker <corey.huinker@gmail.com>
From: Corey Huinker <corey.huinker@gmail.com>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-20T16:07:11Z
Lists: pgsql-hackers
On Wed, Dec 10, 2025 at 12:46 PM Matthias van de Meent < boekewurm+postgres@gmail.com> 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