Re: update behavior
| От | David G. Johnston |
|---|---|
| Тема | Re: update behavior |
| Дата | |
| Msg-id | CAKFQuwbwAbbk6KUKXyX2VxpX3aUDhS5Zd__2JKQXdhH5zHaB4g@mail.gmail.com обсуждение исходный текст |
| Ответ на | update behavior (Scott Ribe <scott_ribe@elevated-dev.com>) |
| Ответы |
Re: update behavior
|
| Список | pgsql-admin |
On Thu, Jun 19, 2025 at 10:24 AM Scott Ribe <scott_ribe@elevated-dev.com> wrote:
I believe that if I UPDATE a row with the same values that it already has, this still dirties pages, writes the row, generates a WAL entry. There is no shortcut in the processing that's "hey, there's not really a change here, we'll just leave storage alone".
Is this correct?
Correct. You need a trigger to prevent the update. There is one provided: suppress_redundant_updates_trigger()
David J.
В списке pgsql-admin по дате отправления: