Re: Add a test for "cannot truncate foreign table"

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add a test for "cannot truncate foreign table"
Date: 2022-07-15 07:52:13
Message-ID: 6c24b79b-2cf7-8137-1c44-e52e7c6facdb@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022/07/08 17:03, Etsuro Fujita wrote:
> Rather than doing so, I'd vote for adding a test case to file_fdw, as
> proposed in the patch, because that would be much simpler and much
> less expensive.

So ISTM that most agreed to push Nagata-san's patch adding the test for TRUNCATE on foreign table with file_fdw. So barring any objection, I will commit the patch.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-07-15 07:56:10 Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Previous Message Simon Riggs 2022-07-15 07:47:58 Re: Allowing REINDEX to have an optional name