From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Murat Tuncer <mtuncer(at)citusdata(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: truncate trigger for foreign data wrappers |
Date: | 2016-08-05 20:44:20 |
Message-ID: | 25235.1470429860@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2016-08-05 16:35:02 -0400, Tom Lane wrote:
>> In particular, it seems to me that rather than implement just this,
>> we really ought to provide an API that lets FDWs actually implement
>> TRUNCATE if they feel like it. Having the trigger and not TRUNCATE
>> capability itself just screams "half baked", wouldn't you say?
> Both is fine with me. I do object to the position that we need an answer
> for all utility commands - that seems like a too high hurdle to pass -
> but implementing truncate for FDWs directly sounds good.
To clarify: I was certainly not suggesting that we need to implement
more than that in the first go. I was just saying that some sort of
long-term roadmap about utility commands for FDWs would be a good idea.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2016-08-05 20:46:01 | Re: Parallel tuplesort (for parallel B-Tree index creation) |
Previous Message | Andres Freund | 2016-08-05 20:41:25 | Re: truncate trigger for foreign data wrappers |