RE: Avoid CommandCounterIncrement in RI trigger when INSERT INTO referencing table

From: "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>
To: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: Avoid CommandCounterIncrement in RI trigger when INSERT INTO referencing table
Date: 2021-03-04 03:41:39
Message-ID: OS0PR01MB5716B8A75E63D86C264856F794979@OS0PR01MB5716.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> From the wiki[1], CCI is to let statements can not see the rows they modify.
Sorry, a typo here "not".
I meant CCI is to let statements can see the rows they modify.

Best regards,
houzj

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2021-03-04 04:00:13 Re: Asynchronous Append on postgres_fdw nodes.
Previous Message Julien Rouhaud 2021-03-04 03:40:17 Re: n_mod_since_analyze isn't reset at table truncation