| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | J Chapman Flack <jflack(at)math(dot)purdue(dot)edu>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Artus de benque <artusdebenque(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Re: Postgresql bug report - unexpected behavior of suppress_redundant_updates_trigger |
| Date: | 2017-06-19 20:59:17 |
| Message-ID: | 20170619205917.vnudxxdyp377e2ji@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Tom Lane wrote:
> As I mentioned upthread, it'd certainly be possible for the trigger
> to iterate through the fields in a datatype-aware fashion and undo
> compression or out-of-lineing before the comparison. But that would
> eat a lot more cycles than the current implementation, and it seems
> dubious that it's worth it. If the trigger is succeeding (ie,
> detecting a no-op update) often enough that it would be worth that,
> you've really got an application-stupidity problem to fix.
ISTM the whole point of suppress_redundant_updates_trigger is to cope
with application stupidity.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-06-19 21:10:47 | Re: [HACKERS] Re: Postgresql bug report - unexpected behavior of suppress_redundant_updates_trigger |
| Previous Message | Tom Lane | 2017-06-19 20:37:27 | Re: [HACKERS] Re: Postgresql bug report - unexpected behavior of suppress_redundant_updates_trigger |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-19 21:06:04 | Re: Getting server crash on Windows when using ICU collation |
| Previous Message | Tom Lane | 2017-06-19 20:37:27 | Re: [HACKERS] Re: Postgresql bug report - unexpected behavior of suppress_redundant_updates_trigger |