| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Kohei KaiGai <kaigai(at)heterodb(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TRUNCATE on foreign tables |
| Date: | 2020-01-07 07:02:57 |
| Message-ID: | 20200107070257.GI2386@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mithun Cy | 2020-01-07 07:22:00 | DROP OWNED CASCADE vs Temp tables |
| Previous Message | Kyotaro Horiguchi | 2020-01-07 06:57:29 | Re: Fetching timeline during recovery |