| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TABLESPACE and directory for Foreign tables? |
| Date: | 2014-05-06 15:09:54 |
| Message-ID: | CA+Tgmob8ZSr3+CNOyZqBhk22qqXEm-SFh3QMGDQHV9Mrj3WJvw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 5, 2014 at 1:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> A larger and more philosophical point is that such a direction of
> development could hardly be called a "foreign" data wrapper. People
> would expect Postgres to take full responsibility for such files,
> including data integrity considerations such as fsync-at-checkpoints
> and WAL support. Even if we wanted the FDW abstractions to allow
> for that, we're very far away from it. And frankly I'd maintain
> that FDW is the wrong abstraction.
The right abstraction, as Josh points out, would probably be pluggable
storage. Are you (or is anyone) planning to pursue that further?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2014-05-06 15:19:56 | Re: New pg_lsn type doesn't have hash/btree opclasses |
| Previous Message | Robert Haas | 2014-05-06 15:05:44 | Re: sb_alloc: a new memory allocator for PostgreSQL |