Re: [HACKERS] [BUGS] Postgresql bug report - unexpected behavior of suppress_redundant_updates_trigger

Поиск
Список
Период
Сортировка
От Dilip Kumar
Тема Re: [HACKERS] [BUGS] Postgresql bug report - unexpected behavior of suppress_redundant_updates_trigger
Дата
Msg-id CAFiTN-tQat3h8qDVH1Z+KpYOL_PwCG0zYDzfbt-YnRxByfhSvw@mail.gmail.com
обсуждение исходный текст
Ответы Re: [HACKERS] [BUGS] Postgresql bug report - unexpected behavior of suppress_redundant_updates_trigger  (Tom Lane <tgl@sss.pgh.pa.us>)
[HACKERS] Re: Postgresql bug report - unexpected behavior ofsuppress_redundant_updates_trigger  (J Chapman Flack <jflack@math.purdue.edu>)
Список pgsql-hackers
Дерево обсуждения 
On Mon, Jun 19, 2017 at 5:20 PM, Artus de benque
<artusdebenque@gmail.com> wrote:
> postgres=# UPDATE test_table SET field = 'hi' WHERE id = 1;
> UPDATE 0
> test_db=# UPDATE test_table SET field = rpad('', 2001, 'a') WHERE id = 1;
> UPDATE 1
> test_db=# UPDATE test_table SET field = rpad('', 2001, 'a') WHERE id = 1;
> UPDATE 1 <--- BUG: expected 0, as we ran the same update twice

Seems like in "suppress_redundant_updates_trigger"  we are comparing
toasted tuple with the new tuple and that is the cause of the bug.


-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] psql's \d and \dt are sending their complaints to different output files
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Preliminary results for proposed new pgindent implementation