Re: Optimization for updating foreign tables in Postgres FDW

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Shigeru Hanada *EXTERN*" <shigeru(dot)hanada(at)gmail(dot)com>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimization for updating foreign tables in Postgres FDW
Date: 2014-07-25 07:39:40
Message-ID: A737B7A37273E048B164557ADEF4A58B17D1FB1B@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Shigeru Hanada wrote:
> * Naming of new behavior
> You named this optimization "Direct Update", but I'm not sure that
> this is intuitive enough to express this behavior. I would like to
> hear opinions of native speakers.

How about "batch foreign update" or "batch foreign modification"?
(Disclaimer: I'm not a native speaker either.)

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2014-07-25 08:35:04 Introducing coarse grain parallelism by postgres_fdw.
Previous Message Etsuro Fujita 2014-07-25 07:30:19 Re: Optimization for updating foreign tables in Postgres FDW