Re: Eliminating SPI from RI triggers - take 2

From: Andres Freund <andres(at)anarazel(dot)de>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: 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-02 01:21:15
Message-ID: 20221002012115.nlg5zxw4tti64qcq@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-09-29 18:18:10 +0900, Amit Langote wrote:
> So, here's a final revision for today. Sorry for the noise.

This appears to fail on 32bit systems. Seems the new test is indeed
worthwhile...

https://cirrus-ci.com/task/6581521615159296?logs=test_world_32#L406

[19:12:24.452] Summary of Failures:
[19:12:24.452]
[19:12:24.452] 2/243 postgresql:main / main/regress FAIL 45.08s (exit status 1)
[19:12:24.452] 4/243 postgresql:pg_upgrade / pg_upgrade/002_pg_upgrade ERROR 71.96s
[19:12:24.452] 32/243 postgresql:recovery / recovery/027_stream_regress ERROR 45.84s

Unfortunately ccf36ea2580f66abbc37f27d8c296861ffaad9bf seems to not have
suceeded in capture the test files of the 32bit build (and perhaps broke it
for 64bit builds as well?), so I can't see the regression.diffs contents.

[19:12:24.387] alter_table ... FAILED 4546 ms
...
[19:12:24.387] ========================
[19:12:24.387] 1 of 211 tests failed.
[19:12:24.387] ========================
[19:12:24.387]
...

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-10-02 01:24:55 Re: Eliminating SPI from RI triggers - take 2
Previous Message Andres Freund 2022-10-02 01:05:55 Re: Tightening behaviour for non-immutable behaviour in immutable functions