Request a Demo
Home   >   mailing lists

Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock) - Mailing list pgsql-hackers

From solai v
Subject Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)
Date
Msg-id CAF0whucM8F2X=+dqZ+R2FiXODQ6rdkRh0uQwKADZa5-BGQFg1g@mail.gmail.com
Whole thread
In response to [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)  (Matthias van de Meent <boekewurm@gmail.com>)
Responses Re: XMLSerialize: version and explicit XML declaration
List pgsql-hackers
Tree view 
Hi Mikhail,
I tested the attached follow-up patch (nocfbot_spgistvischeckwrongtid.patch).
The patch applied cleanly on top of the v02 patch series. PostgreSQL
built successfully, and all regression tests passed .
I also verified that SP-GiST Index Only Scan continued to work
correctly after applying the patch and did not observe any build or
functional regressions during my testing.
I was not able to verify the reported stress-test failure because no
reproducer or stress-test framework was provided.

Regards,
Solai

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: data_checksums + debug_discard_caches = crash
Next
From: solai v
Date:
Subject: Re: XMLSerialize: version and explicit XML declaration