Re: Why is citext/regress failing on hamerkop?

From: Oleg Tselebrovskiy <o(dot)tselebrovskiy(at)postgrespro(dot)ru>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is citext/regress failing on hamerkop?
Date: 2024-08-01 13:37:12
Message-ID: 828b19cef04384da86030d854f01bc64@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro wrote 2024-05-12 06:31:
> Hamerkop is already green on the 15 and 16 branches, apparently
> because it's using the pre-meson test stuff that I guess just didn't
> run the relevant test. In other words, nobody would notice the
> difference anyway, and a master-only fix would be enough to end this
> 44-day red streak.

Sorry for necroposting, but in our automated testing system we have
found some fails of this test. The most recent one was a couple of
days ago (see attached files) on PostgreSQL 15.7. Also I've reported
this bug some time ago [1], but provided an example only for
PostgreSQL 17. Back then the bug was actually found on 15 or 16
branches (no logs remain from couple of months back), but i wanted
to show that it was reproducible on 17.

I would appreciate if you would backpatch this change to 15 and 16
branches.

[1]
https://www.postgresql.org/message-id/6885a0b52d06f7e5910d2b6276bbb4e8%40postgrespro.ru

Oleg Tselebrovskiy, Postgres Pro

Attachment Content-Type Size
initdb.log text/plain 1.1 KB
postmaster.log text/plain 668 bytes
regression.diffs text/x-diff 540 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2024-08-01 13:54:52 Re: can we mark upper/lower/textlike functions leakproof?
Previous Message Amul Sul 2024-08-01 13:18:42 Re: pg_verifybackup: TAR format backup verification