Re: simplifying foreign key/RI checks

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: simplifying foreign key/RI checks
Date: 2021-01-25 09:19:56
Message-ID: CA+HiwqFPXVSozQBW6LBsW8jek9Z4i4M-aYVEb59CLHjUh5Xtpg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 25, 2021 at 9:24 AM Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
> On Sun, Jan 24, 2021 at 6:51 AM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>> Here's v5.
>
> v5 patches apply to master.
> Suggested If/then optimization is implemented.
> Suggested case merging is implemented.
> Passes make check and make check-world yet again.
> Just to confirm, we don't free the RI_CompareHashEntry because it points to an entry in a hash table which is TopMemoryContext aka lifetime of the session, correct?

Right.

> Anybody else want to look this patch over before I mark it Ready For Committer?

Would be nice to have others look it over. Thanks.

--
Amit Langote
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tsunakawa.takay@fujitsu.com 2021-01-25 09:20:29 RE: libpq debug log
Previous Message Bharath Rupireddy 2021-01-25 09:18:28 Re: Identify missing publications from publisher while create/alter subscription.