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

From Kazutaka Onishi
Subject Re: TRUNCATE on foreign table
Date
Msg-id CAJuF6cP+c2UW8uyofoyh7JeWSj5GuMPfXTy1DF-uK6HLSe=-3g@mail.gmail.com
Whole thread Raw
In response to Re: TRUNCATE on foreign table  (Zhihong Yu <zyu@yugabyte.com>)
Responses Re: TRUNCATE on foreign table
List pgsql-hackers
Thank you for your comment! :D
I have fixed it and attached the revised patch.

regards,



2021年2月7日(日) 2:08 Zhihong Yu <zyu@yugabyte.com>:
Hi,
+               if (strcmp(defel->defname, "truncatable") == 0)
+                   server_truncatable = defGetBoolean(defel);

Looks like we can break out of the loop when the condition is met.

+           /* ExecForeignTruncate() is invoked for each server */

The method name in the comment is slightly different from the actual method name.

+           if (strcmp(defel->defname, "truncatable") == 0)
+               truncatable = defGetBoolean(defel);

We can break out of the loop when the condition is met.

Cheers

On Sat, Feb 6, 2021 at 5:11 AM Kazutaka Onishi <onishi@heterodb.com> wrote:
Hello, 

The attached patch is for supporting "TRUNCATE" on  foreign tables.

This patch includes:
* Adding "ExecForeignTruncate" function into FdwRoutine.
* Enabling "postgres_fdw" to use TRUNCATE.

This patch was proposed by Kaigai-san in March 2020, 
but it was returned because it can't be applied to the latest source codes.

Please refer to the discussion.

I have fixed the patch due to submit it to Commit Fest 2021-03.  

regards,

--
------------------
Kazutaka Onishi


--
------------------
Kazutaka Onishi


--
------------------
Kazutaka Onishi
Attachment

pgsql-hackers by date:

Previous
From: Greg Nancarrow
Date:
Subject: Re: Bug in query rewriter - hasModifyingCTE not getting set
Next
From: Bharath Rupireddy
Date:
Subject: Re: Is Recovery actually paused?