| 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-16 09:40:53 |
| Message-ID: | OS0PR01MB57166652FA53A04624D15F00946B9@OS0PR01MB5716.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> To support parallel insert into FK relation.
> There are two scenarios need attention.
> 1) foreign key and primary key are on the same table(INSERT's target table).
> (referenced and referencing are the same table)
> 2) referenced and referencing table are both partition of INSERT's target table.
> (These cases are really rare for me)
>
> In the two cases, the referenced table could be modified when INSERTing and
> CCI is necessary, So, I think we should treat these cases as parallel restricted
> while doing safety check.
>
> Attaching V1 patch that Implemented above feature and passed regression
> test.
Attaching rebased patch based on HEAD.
Best regards,
houzj
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0002-extend-safery-check-for-fk-relation.patch | application/octet-stream | 6.6 KB |
| v2-0001-skip-cci.patch | application/octet-stream | 11.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Guo | 2021-03-16 09:44:26 | Re: fdatasync performance problem with large number of DB files |
| Previous Message | Bharath Rupireddy | 2021-03-16 09:38:04 | Re: A new function to wait for the backend exit after termination |