| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 18:04:06 |
| Message-ID: | 20160805180406.hes2hwfh5k4vivxn@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-08-05 13:32:18 -0400, Robert Haas wrote:
> I think if we're going to add support utility commands on foreign
> tables, we ought to think about all of the different utility commands
> that someone might want and what exactly we want the behavior to be.
> For example, consider CLUSTER or CREATE INDEX or VACUUM or ANALYZE.
> We might interpret TRUNCATE or CLUSTER as a request to dispatch the
> same request for the remote side, but ANALYZE can't mean that: it has
> to mean gather local statistics. And what if the other side is not PG
> and supports other operations that we don't have, like OPTIMIZE TABLE
> or DISENGAGE FTL?
That's not really comparable imo - we don't have triggers for those
locally either. For better or worse we've decided that TRUNCATE is more
like DML than DDL.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-08-05 18:05:02 | Re: truncate trigger for foreign data wrappers |
| Previous Message | Pavan Deolasee | 2016-08-05 18:00:26 | Re: Heap WARM Tuples - Design Draft |