| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Alexander Korotkov *EXTERN*" <aekorotkov(at)gmail(dot)com>, "Kohei KaiGai" <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | "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 08:05:01 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C208A4EF7A@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-11-08 08:07:14 | Re: Fix errcontext() function |
| Previous Message | Tom Lane | 2012-11-08 06:36:54 | Re: commit 1eb1dde049ccfffc42c80c2 broke make -j2 |