Re: TRUNCATE on foreign tables - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: TRUNCATE on foreign tables
Date
Msg-id 20200107070257.GI2386@paquier.xyz
Whole thread Raw
In response to Re: TRUNCATE on foreign tables  (Stephen Frost <sfrost@snowman.net>)
Responses Re: TRUNCATE on foreign tables
List pgsql-hackers
On Mon, Jan 06, 2020 at 04:32:39PM -0500, Stephen Frost wrote:
> RESTRICT, yes.  I don't know about ONLY being sensible as we don't
> really deal with inheritance and foreign tables very cleanly today, as I
> said up-thread, so I'm not sure if we really want to put in the effort
> that it'd require to figure out how to make ONLY make sense.

True enough.

> The question about how to handle IDENTITY is a good one.  I suppose
> we could just pass that down and let the FDW sort it out..?

Looking at the code, ExecuteTruncateGuts() passes down restart_seqs,
so it sounds sensible to me to just pass down that to the FDW
callback and the callback decide what to do.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Fetching timeline during recovery
Next
From: Mithun Cy
Date:
Subject: DROP OWNED CASCADE vs Temp tables