| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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:17:52 |
| Message-ID: | CA+HiwqH9R0SfoySeWFfZeJHQ-w5BU4mYyezKPz-tQYbxWPBt6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 7, 2022 at 19:15 Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> 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.
Ah, that’s right. Will do so, thanks for the suggestion.
> --
Thanks, Amit Langote
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bt22nakamorit | 2022-10-07 10:41:16 | Re: Make ON_ERROR_STOP stop on shell script failure |
| Previous Message | Alvaro Herrera | 2022-10-07 10:15:44 | Re: Eliminating SPI from RI triggers - take 2 |