From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Petr Jelinek <petr(dot)jelinek(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Subject: | Re: Decoding speculative insert with toast leaks memory |
Date: | 2021-06-08 11:46:26 |
Message-ID: | CAFiTN-v5Fvn3=pwAY8PH9jPMYcENzzESZG701WRecKe89=1+ZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 7, 2021 at 6:45 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>>
>>
>> 2. In the test, there seems to be an assumption that we can unlock s2
>> and s3 one after another, and then both will start waiting on s-1 but
>> isn't it possible that before s2 start waiting on s1, s3 completes its
>> insertion and then s2 will never proceed for speculative insertion?
>
>
> I agree, such race conditions are possible. Currently, I am not able to think what we can do here, but I will think more on this.
>
Based on the off list discussion, I have modified the test based on
the idea showed in
"isolation/specs/insert-conflict-specconflict.spec", other open point
we had about the race condition that how to ensure that when we unlock
any session it make progress, IMHO the isolation tested is designed in
a way that either all the waiting session returns with the output or
again block on a heavy weight lock before performing the next step.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
v4-0001-Bug-fix-for-speculative-abort.patch | text/x-patch | 6.0 KB |
v4-0002-test-case.patch | text/x-patch | 13.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias van de Meent | 2021-06-08 11:54:41 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |
Previous Message | Justin Pryzby | 2021-06-08 11:33:33 | Re: pg14b1 stuck in lazy_scan_prune/heap_page_prune of pg_statistic |