On 08-Nov-2012, at 13:35, "Albe Laurenz" <laurenz.albe@wien.gv.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@postgresql.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
erroron PostgreSQL side.exposing this as a table option is IMHO a bit risky, and the user may not know whether the
foreigndata source will accept writes or not.
Atri
