Re: [v9.3] writable foreign tables

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: Alexander Korotkov *EXTERN* <aekorotkov(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>
Subject: Re: [v9.3] writable foreign tables
Date: 2012-11-08 14:53:11
Message-ID: 577511D2-CFC8-4FE7-8066-4FE633904058@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08-Nov-2012, at 13:35, "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:

> Alexander Korotkov wrote:
>> 2) You wrote that FDW can support or don't support write depending on
> having corresponding functions.
>> However it's likely some tables of same FDW could be writable while
> another are not. I think we should
>> have some mechanism for FDW telling whether particular table is
> writable.
>
> I think that this would best be handled by a table option,
> if necessary.
> That allows maximum flexibility for the design of the FDW.
> In many cases it might be enough if the foreign data source
> raises an error on a write request.
>
> Yours,
> Laurenz Albe
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

+1

I agree, we should have a system where if the foreign data source raises an error on write, FDW can raise corresponding error on PostgreSQL side.exposing this as a table option is IMHO a bit risky, and the user may not know whether the foreign data source will accept writes or not.

Atri

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2012-11-08 15:01:29 Re: Proposal for Allow postgresql.conf values to be changed via SQL
Previous Message Amit Kapila 2012-11-08 14:53:10 Re: Proposal for Allow postgresql.conf values to be changed via SQL