| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | "Andrey V(dot) Lepikhov" <a(dot)lepikhov(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com> |
| Subject: | Re: SEGFAULT on a concurrent UPDATE of mix of local and foreign partitions |
| Date: | 2021-08-12 08:38:42 |
| Message-ID: | 540a2616-c32d-47b2-0d6c-ad62b66ba937@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 10/08/2021 12:18, Andrey V. Lepikhov wrote:
> On 8/10/21 1:29 AM, Heikki Linnakangas wrote:
>> Does it ever make sense to re-evaluate a direct Foreign Update as part
>> of EvalPlanQual? It doesn't seem sane to me, you cannot just run an
>> UPDATE statement again and expect it to be idempotent. So I think it
>> would make sense skip this during EvalPlanQual processing altogether.
>> And no need to call the FDW's Begin/EndDirectModify functions either.
> Agree. It is my first dive into the EPQ code. After studying i think
> this makes no sense.
Pushed the fix to master and v14. Thanks for the report!
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhéxué M. | 2021-08-12 18:38:47 | Postgresql - Service hangs.... |
| Previous Message | vilarion | 2021-08-12 08:01:56 | Re: BUG #17142: COPY ignores client_encoding for octal digit characters |