Re: postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgres_fdw: Oddity in pushing down inherited UPDATE/DELETE joins to remote servers
Date: 2018-05-11 07:19:29
Message-ID: 6c9f2b85-2503-b761-bf4f-aa8857d71990@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018/05/11 16:12, Amit Langote wrote:
> Just to clarify, does this problem only arise because there is a pushed
> down join involving the child? That is, does the problem only occur as of
> the following commit:
>
> commit 1bc0100d270e5bcc980a0629b8726a32a497e788
> Author: Robert Haas <rhaas(at)postgresql(dot)org>
> Date: Wed Feb 7 15:34:30 2018 -0500
>
> postgres_fdw: Push down UPDATE/DELETE joins to remote servers.
>
> In other words, do we need to back-patch this up to 9.5 which added
> foreign table inheritance?

Oops, it should have been clear by the subject line that the problem
didn't exist before that commit. Sorry.

Thanks,
Amit

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-05-11 08:45:20 Re: [HACKERS] asynchronous execution
Previous Message Ashutosh Bapat 2018-05-11 07:17:55 Re: Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled.