| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Eliminating SPI from RI triggers - take 2 |
| Date: | 2022-10-07 10:15:44 |
| Message-ID: | 20221007101544.546gjbl5x5g65zh5@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Oct-07, Amit Langote wrote:
> > Thanks for the heads up. Hmm, this I am not sure how to reproduce on
> > my own, so I am currently left with second-guessing what may be going
> > wrong on 32 bit machines with whichever of the 4 patches.
> >
> > For now, I'll just post 0001, which I am claiming has no semantic
> > changes (proof pending), to rule out that that one's responsible.
>
> Nope, not 0001. Here's 0001+0002.
Please note that you can set up a github repository so that cirrus-ci
tests whatever patches you like, without having to post them to
pg-hackers. See src/tools/ci/README, it takes three minutes if you
already have the account and repository.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2022-10-07 10:17:52 | Re: Eliminating SPI from RI triggers - take 2 |
| Previous Message | Amit Langote | 2022-10-07 09:56:37 | Re: Eliminating SPI from RI triggers - take 2 |