Re: Optimization for updating foreign tables in Postgres FDW

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Etsuro Fujita *EXTERN*" <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimization for updating foreign tables in Postgres FDW
Date: 2015-03-04 07:58:32
Message-ID: A737B7A37273E048B164557ADEF4A58B365A2C3A@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Etsuro Fujita wrote:
> While updating the patch, I noticed that in the previous patch, there is
> a bug in pushing down parameterized UPDATE/DELETE queries; generic plans
> for such queries fail with a can't-happen error. I fixed the bug and
> tried to add the regression tests that execute the generic plans, but I
> couldn't because I can't figure out how to force generic plans. Is
> there any way to do that?

I don't know about a way to force it, but if you run the statement six
times, it will probably switch to a generic plan.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2015-03-04 07:59:33 Re: Reduce pinning in btree indexes
Previous Message Etsuro Fujita 2015-03-04 07:50:42 Re: Optimization for updating foreign tables in Postgres FDW