Re: pgsql: Rewrite some RI code to avoid using SPI

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Rewrite some RI code to avoid using SPI
Date: 2022-04-07 22:00:29
Message-ID: 3494463.1649368829@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2022-Apr-07, Tom Lane wrote:
>> (1) We've added enough instability to the tree this week already.

> Several animals failed already in ways that look obviously connected to
> this commit, so I can't disagree:

Yeah, I saw that after complaining. Looks like all and only the
32-bit animals were unhappy. Something we'll want to run to ground
when there's less time pressure.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-04-07 22:26:33 pgsql: Extend plsample example to include a trigger handler.
Previous Message Andres Freund 2022-04-07 21:54:57 pgsql: Add minimal tests for recovery conflict handling.