From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
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 16:48:36 |
Message-ID: | 20415.1399394916@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 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?
Well, as you've noticed, I made no progress on that since last PGCon.
It's still something I'm thinking about, but it's a hard problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-05-06 16:50:43 | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |
Previous Message | Simon Riggs | 2014-05-06 16:43:45 | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |