On 7/29/15 2:40 PM, Alvaro Herrera wrote:
Qingqing Zhou wrote:
Can we simplify above with foreign table methods? There are two major
concerns about this method per previous discussions: security and
usability. I think the main cause is the sharing foreign table design.
I think foreign data wrappers are great. I do not think that we should
try to shape every problem to look like foreign data so that we can
solve it with a foreign data wrapper. I am a bit nervous that this
keeps being brought up.
Agreed.
I think a better option would be shoving it into a backend tuplestore
and just leaving it there (maybe with a command to clear it for the
paranoid). That gives a relation you can query against, insert into
another table, etc.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
