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 -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers