Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
От
Dean Rasheed
Тема
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
Дата
Msg-id
CAEZATCUHSyk0U=r_jM1gcLscjopgsmTojxvATro9ZfncPsfPjg@mail.gmail.com
Ответ на
Список
Дерево обсуждения
BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access PG Bug reporting form <noreply@postgresql.org>
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access jian he <jian.universality@gmail.com>
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access jian he <jian.universality@gmail.com>
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access Dean Rasheed <dean.a.rasheed@gmail.com>
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access Richard Guo <guofenglinux@gmail.com>
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access Dean Rasheed <dean.a.rasheed@gmail.com>
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access Richard Guo <guofenglinux@gmail.com>
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access jian he <jian.universality@gmail.com>
Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access Dean Rasheed <dean.a.rasheed@gmail.com>
On Wed, 13 Dec 2023 at 03:36, jian he wrote: > > your patch is correct, especially ExecCrossPartitionUpdate canSetTag > logic is very intuitive to me. > Thanks for checking. Patch pushed and back-patched. > +SELECT * FROM pa_target ORDER BY tid; > I would change to > > SELECT pt.*, pg_get_expr(pc.relpartbound, pt.tableoid, TRUE) > FROM pa_target pt > JOIN pg_class pc ON pc.oid = pt.tableoid > ORDER BY val,tid; > > that would make the result more understandable, maybe i am over engineering. > Anyway, that's my personal preference. I decided not to do that, just to keep it simpler, and consistent with the preceding tests. Regards, Dean
В списке pgsql-bugs по дате отправления
От: PG Bug reporting form
Дата:
От: PG Bug reporting form
Дата: