| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'vignesh C' <vignesh21(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Review items for EXCEPT TABLE publication |
| Date: | 2026-09-10 11:41:14 |
| Message-ID: | OS9PR01MB12149EF8749C5B4AF04FCE27BF5BF2@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Vignesh,
> Thanks kuroda-san. I have addressed this in the v2 version patch
> attached, however I did not change the lock mode and used the existing
> AccessShareLock mode itself as I felt that should suffice. This
> approach also addresses Chao's comments from [1].
My intention was similar but can we unify codes for re-validation?
My idea attached here could be applied atop v2.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| Attachment | Content-Type | Size |
|---|---|---|
| v2_kuroda.diffs | application/octet-stream | 3.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2026-09-10 11:45:03 | Re: CI slowdown due to PG_TEST_INITDB_EXTRA_OPTS |
| Previous Message | Xuneng Zhou | 2026-09-10 11:31:06 | Re: Improve WAIT FOR read-your-writes consistency doc |