Re: Segmentation Fault in logical decoding get/peek API

From: Sudalai <sudalait2(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Segmentation Fault in logical decoding get/peek API
Date: 2018-02-21 07:18:58
Message-ID: 1519197538224-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>>And if it's segfaulting, it has to mean specinsert is NULL. So either we
>>never got REORDER_BUFFER_CHANGE_INTERNAL_SPEC_INSERT, or we threw it
>>away in the "change_done" part. Seems strange in both cases.

Yes, specinsert is NULL.

>> Sudalai, are you using speculative inserts in the transaction?
Yes . We have done ON CONFLICT DO NOTHING .

Is it correct to add below check ,
if(specinsert == NULL ){
goto change_done;
}
before , Assert(specinsert->data.tp.oldtuple == NULL); to fix segfault ?

Is specinsert is NULL, because of CONFLICT DO NOTHING ?

Thanks for the response Tomas, Peter.

-----
sudalai
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Victor Yegorov 2018-02-21 09:46:30 Re: pg_upgrade and materialized views
Previous Message Peter Geoghegan 2018-02-21 01:20:40 Re: Segmentation Fault in logical decoding get/peek API