Re: BUG #5063: MS Access crashes by quiting after linking tables with PostgreSQL - Mailing list pgsql-bugs

From Russell Smith
Subject Re: BUG #5063: MS Access crashes by quiting after linking tables with PostgreSQL
Date
Msg-id 4ABBEA9C.5000103@pws.com.au
Whole thread Raw
In response to Re: BUG #5063: MS Access crashes by quiting after linking tables with PostgreSQL  (Annita Veneti <annita.veneti@qs-unisolution.com>)
Responses Re: BUG #5063: MS Access crashes by quiting after linking tables with PostgreSQL  (Annita Veneti <annita.veneti@qs-unisolution.com>)
List pgsql-bugs
Annita Veneti wrote:
> Matt you are absolutely right! The msysconf is not related...
> Yesterday I did some test and have seen that the access is working fine with postgres as long as the SSL mode is
disable,as soon as I put it enabled then it crashes on shutdown.... 
>
> Go figure!!!
>
> Any ideas?
>
What version of the PostgreSQL client libraries are you running.  There
is a bug in anything before 8.4 that would unlink libpq from memory and
not remove the SSL callback functions in that code.  When other
libraries attempt to shutdown their SSL, it crashes as those functions
point to invalid memory.  I've not seen this on the Windows platform
personally yet.  But I have seen it running php on linux.  Have a look
at " libpq does not manage SSL callbacks properly when other libraries
are involved." reported by me on 25/6/08.

Regards

Russell

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5078: returns setof functions fails after table structure altered
Next
From: Michael Brown
Date:
Subject: Re: Postgresql 8.4.1 segfault, backtrace