Re: update with no changes
| От | Marcos Pegoraro |
|---|---|
| Тема | Re: update with no changes |
| Дата | |
| Msg-id | CAB-JLwZ66E+1siJBn2TC+_5hkdjB=jp54vDU68CCGX3RNzyOjQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: update with no changes ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Ответы |
Re: update with no changes
Re: update with no changes |
| Список | pgsql-hackers |
Because it takes resources to determine that nothing changed. If you want to opt-in into that there is even an extension trigger that makes doing so fairly simple. But it's off by default because the typical case is that people don't frequently perform no-op updates so why eat the expense.
But it takes resources for other operations, right ?
I think this is not unusual. If an user double click on a grid, just sees a record and clicks ok to save, probably that application calls an update instead of seeing if some field were changed before that.
В списке pgsql-hackers по дате отправления: