On Tue, 16 Apr 2024 at 18:58, Robins Tharakan <thara...@gmail.com> wrote:
> The last 25 consecutive runs have passed [1] after switching
> REL_12_STABLE to -O0 ! So I am wondering whether that confirms that
> the compiler version is to blame, and while we're still here,
> is there anything else I could try?
I don't think it's conclusive proof that it's a compiler bug. -O0
could equally just have changed the timing sufficiently to not trigger
the issue.
It might be a long shot, but I wonder if it might be worth running a
workload such as:
psql -c "create table a (a int primary key, b text not null, c int not
null); insert into a values(1,'',0);" postgres
echo "update a set b = repeat('a', random(1,10)), c=c+1 where a = 1;"
> bench.sql
pgbench -n -t 12500 -c 8 -j 8 -f bench.sql postgres
psql -c "table a;" postgres
On a build with the original CFLAGS. I expect the value of "c" to be
100k after running that. If it's not then something bad has happened.
That would exercise the locking code heavily and would show us if any
updates were missed due to locks not being correctly respected or seen
by other backends.
David
