Re: More efficient RI checks - take 2

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Antonin Houska <ah(at)cybertec(dot)at>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: More efficient RI checks - take 2
Date: 2020-04-22 19:13:19
Message-ID: CADkLM=fuQbAMtwc0=2POyxn1wsKAPh73o85FjJPxY2KFK+Ka2Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 22, 2020 at 2:36 PM Andres Freund <andres(at)anarazel(dot)de> wrote:

> Hi,
>
> On 2020-04-22 13:46:22 -0400, Robert Haas wrote:
> > On Wed, Apr 22, 2020 at 1:18 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
> wrote:
> > > Well, I was actually thinking in building ready-made execution trees,
> > > bypassing the planner altogether. But apparently no one thinks that
> > > this is a good idea, and we don't have any code that does that already,
> > > so maybe it's not a great idea.
>
> I was commenting on what I understood Corey to say, but was fairly
> unclear about it. But I'm also far from sure that I understood Corey
> correctly...
>

I was unclear because, even after my failed foray into statement level
triggers for RI checks, I'm still pretty inexperienced in this area.

I'm just happy that it's being discussed.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-04-22 19:29:29 Re: Header / Trailer Comment Typos for M4 macros
Previous Message Alvaro Herrera 2020-04-22 19:07:38 Re: 2pc leaks fds