| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: simplifying foreign key/RI checks |
| Date: | 2021-08-30 04:36:12 |
| Message-ID: | CADkLM=cYanWQsJ54JtrWZKSPtF7+amHyQdwyjYtZgZWz-bBXBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> Rebased patches attached.
I'm reviewing the changes since v6, which was my last review.
Making ExecLockTableTuple() it's own function makes sense.
Snapshots are now accounted for.
The changes that account for n-level partitioning makes sense as well.
Passes make check-world.
Not user facing, so no user documentation required.
Marking as ready for committer again.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-08-30 04:58:00 | Re: create table like: ACCESS METHOD |
| Previous Message | Tom Lane | 2021-08-30 04:21:44 | Re: jff: checksum algorithm is not as intended |