Horton
Menu

Re: [v9.3] writable foreign tables

Albe Laurenz <laurenz.albe@wien.gv.at>

View thread
From: "Albe Laurenz" <laurenz.albe@wien.gv.at>
To: "Alexander Korotkov *EXTERN*" <aekorotkov@gmail.com>, "Kohei KaiGai" <kaigai@kaigai.gr.jp>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>, "Robert Haas" <robertmhaas@gmail.com>, "PgHacker" <pgsql-hackers@postgresql.org>, "Shigeru Hanada" <shigeru.hanada@gmail.com>
Date: 2012-11-08T08:05:01Z
Lists: pgsql-hackers 
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix postgres_fdw's issues with inconsistent interpretation of data values.