On Tue, Feb 9, 2021 at 7:45 PM Kazutaka Onishi <oni...@heterodb.com> wrote: > > > IIUC, "truncatable" would be set to "false" for relations which do not > > have physical storage e.g. views but will be true for regular tables. > > "truncatable" option is just for the foreign table and it's not related with > whether it's on a physical storage or not. > "postgres_fdw" already has "updatable" option to make the table read-only. > However, "updatable" is for DML, and it's not suitable for TRUNCATE. > Therefore new options "truncatable" was added. > > Please refer to this message for details. > https://www.postgresql.org/message-id/20200128040346.GC1552%40paquier.xyz > > > DELETE is very different from TRUNCATE. Application may want to DELETE > > based on a join with a local table and hence it can not be executed on > > a foreign server. That's not true with TRUNCATE. > > Yeah, As you say, Applications doesn't need TRUNCATE. > We're focusing for analytical use, namely operating huge data. > TRUNCATE can erase rows faster than DELETE.
The question is why can't that truncate be run on the foreign server itself rather than local server? -- Best Wishes, Ashutosh Bapat
