Re: BUG #5063: MS Access crashes by quiting after linking tables with PostgreSQL

From: Russell Smith <mr-russ(at)pws(dot)com(dot)au>
To: Annita Veneti <annita(dot)veneti(at)qs-unisolution(dot)com>
Cc: Matt Taylor <matt(at)lindenelevator(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5063: MS Access crashes by quiting after linking tables with PostgreSQL
Date: 2009-09-24 21:54:36
Message-ID: 4ABBEA9C.5000103@pws.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Brown 2009-09-24 22:07:49 Re: Postgresql 8.4.1 segfault, backtrace
Previous Message Tom Lane 2009-09-24 17:35:29 Re: BUG #5078: returns setof functions fails after table structure altered