Re: Support TRUNCATE triggers on foreign tables

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Support TRUNCATE triggers on foreign tables
Date: 2022-07-12 00:24:20
Message-ID: e7c99731-a078-cae5-ddac-5d2948323854@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022/07/08 17:13, Ian Lawrence Barwick wrote:
>> If we want to add such prevention, we will need similar checks for
>> INSERT/DELETE/UPDATE not only TRUNCATE. However, I think such fix is independent
>> from this and it can be proposed as another patch.
>
> Ah OK, makes sense from that point of view. Thanks for the clarification!

So I pushed the v2 patch that Yugo-san posted. Thanks!

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 Masahiko Sawada 2022-07-12 00:48:52 Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Previous Message Andres Freund 2022-07-11 23:21:57 Re: making relfilenodes 56 bits