| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Ronan Dunklau <rdunklau(at)gmail(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Triggers on foreign tables |
| Date: | 2013-10-16 18:32:08 |
| Message-ID: | CA+TgmobhTxyJWf36jMvZEn2-ZuUYmr1+mqwQioKGHBw3S0tAyg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 16, 2013 at 2:20 PM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
>> True, but gosh, updates via file_fdw are gonna be so slow I can't
>> believe anybody'd use it for something real....
>>
> How about another example? I have implemented a column-oriented
> data store with read/write capability, using FDW APIs.
> The role of FDW driver here is to translate its data format between
> column-oriented and row-oriented, but no trigger capability itself.
OK, that's a believable example. Call me convinced. :-)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-10-16 18:34:59 | Re: Turning recovery.conf into GUCs |
| Previous Message | Robert Haas | 2013-10-16 18:30:34 | better atomics |