Re: TABLESPACE and directory for Foreign tables? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: TABLESPACE and directory for Foreign tables?
Date
Msg-id CA+Tgmob8ZSr3+CNOyZqBhk22qqXEm-SFh3QMGDQHV9Mrj3WJvw@mail.gmail.com
Whole thread Raw
In response to Re: TABLESPACE and directory for Foreign tables?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TABLESPACE and directory for Foreign tables?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, May 5, 2014 at 1:53 PM, Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: sb_alloc: a new memory allocator for PostgreSQL
Next
From: Vik Fearing
Date:
Subject: Re: New pg_lsn type doesn't have hash/btree opclasses