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

From Kazutaka Onishi
Subject Re: TRUNCATE on foreign table
Date
Msg-id CAJuF6cNVJC5+C2ci0FCgJBpSX8NZF+eaMTbcboDRtTPyagUttA@mail.gmail.com
Whole thread Raw
In response to Re: TRUNCATE on foreign table  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: TRUNCATE on foreign table
List pgsql-hackers
> 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.

> 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.

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Routine usage information schema tables
Next
From: Fujii Masao
Date:
Subject: ERROR: invalid spinlock number: 0