Re: [BUGS] Segmentation fault in libpq

On 07/02/2017 09:12 PM, Andres Freund wrote:
> Hi,
>
> On 2017-07-02 20:58:52 +0200, Michal Novotný wrote:
>> thank you all for your advice. I've been investigating this a little more
>> and finally it turned out it's not a bug in libpq although I got confused
>> by going deep as several libpq functions. The bug was really on our side
>> after trying to use connection pointer after calling PQfinish(). The code
>> is pretty complex so it took some time to investigate however I would like
>> to apologize for "blaming" libpq instead of our code.
> Usually using a tool like valgrind is quite helpful to find issues like
> that, because it'll show you the call-stack accessing the memory and
> *also* the call-stack that lead to the memory being freed.
>
> - Andres

Well, I've tried but I was unable to locate the issue so I had to
investigate the code our little further and finally I've been able to
find the issue.

Thanks again,
Michal

--
Michal Novotny
System Development Lead
michal(dot)novotny(at)greycortex(dot)com

GREYCORTEX s.r.o.
Purkynova 127, 61200 Brno
Czech Republic
www.greycortex.com