From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Eliot Gable <egable+pgsql-general(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Foreign Tables |
Date: | 2011-11-16 21:58:16 |
Message-ID: | 1321480696.2238.6.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2011-11-16 at 13:38 -0500, Eliot Gable wrote:
> I am working on a reporting project where I need to generate a report based
> on data from several different network appliances. Each appliance runs a
> PostgreSQL database which houses all of the information for the appliance.
> Further, there are dozens of triggers in the database which fire when
> various tables are touched in various different ways (insert, update,
> delete). These triggers currently are used to build materialized views of
> much of the data that I want to summarize in the reports.
>
> I have read as much as I can find on 9.1's foreign table support, and it
> looks almost ideal for bridging the gap between all the databases and
> collecting all the data into a single report. However, I am unclear on a
> few points...
>
> 1a) Can the foreign tables be written to? For example, I have server1 with
> table foo and server2 which does 'create foreign table bar' where bar
> references server1.foo. Can server2 write to bar and have it show in
> server1.foo?
>
No, you can't (yet?).
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Arctic Toucan | 2011-11-16 22:07:50 | Transaction wraparound problem due to wrong datfrozenxid? |
Previous Message | Adam Cornett | 2011-11-16 18:48:30 | Re: all non-PK columns from information schema |