From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: update with no changes |
Date: | 2021-11-19 20:09:36 |
Message-ID: | CAB-JLwY8Fvd1VA15wsRKPEC1ynhsXhSmswyBj1zxdLK3iF1wzw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> I suppose if the application side cannot be trusted to code to a
> specification without having the server side add validation and/or
> compensation code to catch the bugs then, yes, one option is to have the
> server side do extra work. There are other solutions, some of which are
> not even technical in nature.
>
> Just to show you my problem, since I wrote my first email of this
discussion, I changed a little my auditing trigger to get total of records
being updated. Only last 3 or 4 hours we´re talking, we had 12% of them
with no changes. It is a lot.
Thanks again, we have a huge code review here.
regards,
Marcos
From | Date | Subject | |
---|---|---|---|
Next Message | Melanie Plageman | 2021-11-19 20:11:57 | Re: Avoiding smgrimmedsync() during nbtree index builds |
Previous Message | Alvaro Herrera | 2021-11-19 19:59:12 | Re: xlog.c: removing ReadRecPtr and EndRecPtr |