Re: truncate trigger for foreign data wrappers - Mailing list pgsql-hackers

From Andres Freund
Subject Re: truncate trigger for foreign data wrappers
Date
Msg-id 20160805143918.uwqeqkrkyzl6s4sn@alap3.anarazel.de
Whole thread Raw
In response to Re: truncate trigger for foreign data wrappers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: truncate trigger for foreign data wrappers  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2016-08-05 10:33:49 -0400, Tom Lane wrote:
> Murat Tuncer <mtuncer@citusdata.com> writes:
> > I recently hit a road blocker when I tried to create a truncate trigger on
> > a foreign table. trigger.c::CreateTrigger() function has explicit check to
> > block truncate trigger on foreign tables.
> 
> That's good, because we don't implement TRUNCATE on foreign tables: there
> is nothing in the FDW API that would support it.  Not much point in
> declaring a trigger for an event that can never happen.

Well, allowing BEFORE triggers to return NULL or something, preventing
the execution of the rest, would be such an implementation, and also
independently useful.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: truncate trigger for foreign data wrappers
Next
From: Kenneth Marshall
Date:
Subject: Hash index with larger hashes