Re: Corruption with IMMUTABLE functions in index expression.

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Corruption with IMMUTABLE functions in index expression.
Date: 2021-10-11 16:26:09
Message-ID: 034eb9d6-4ac5-13e1-6e19-ae720dd88cb7@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/11/21 18:08, Andrey Borodin wrote:
>
>
>> 11 окт. 2021 г., в 20:47, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> написал(а):
>>
>> On Monday, October 11, 2021, Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com> wrote:
>> While using IMMUTABLE functions in index expression, we are getting below corruption on HEAD.
>>
>> That function is not actually immutable (the system doesn’t check whether your claim of immutability and the function definition match, its up to you to know and specify the correct label for what the function does) so not our problem. Write a trigger instead.
> +1, but the error is strange. This might be a sign of some wrong assumption somewhere. My wild guess is that metapage is read before it was written.
>

True, but I can't reproduce it. So either the build is broken in some
way, or perhaps there's something else going on. What would be quite
helpful is a backtrace showing why the error was triggered. i.e. set a
breakpoint on the ereport in mdread().

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-10-11 16:27:44 Re: Corruption with IMMUTABLE functions in index expression.
Previous Message Andrey Borodin 2021-10-11 16:08:18 Re: Corruption with IMMUTABLE functions in index expression.