Re: Segmentation Fault in logical decoding get/peek API - Mailing list pgsql-bugs

From Sudalai
Subject Re: Segmentation Fault in logical decoding get/peek API
Date
Msg-id 1519197538224-0.post@n3.nabble.com
Whole thread Raw
In response to Re: Segmentation Fault in logical decoding get/peek API  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Segmentation Fault in logical decoding get/peek API  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List 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


pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Segmentation Fault in logical decoding get/peek API
Next
From: Victor Yegorov
Date:
Subject: Re: pg_upgrade and materialized views