From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Rewrite some RI code to avoid using SPI
Date: Thu, 07 Apr 2022 18:00:29 -0400
Message-ID: <3494463.1649368829@sss.pgh.pa.us> (raw)
In-Reply-To: <202204072134.sou3laebxj7c@alvherre.pgsql>
References: <202204072134.sou3laebxj7c@alvherre.pgsql>
Alvaro Herrera <alvherre@alvh.no-ip.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Rewrite some RI code to avoid using SPI
In-Reply-To: <3494463.1649368829@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox