up
> on the open items list so we don't miss it? It's a pretty major issue.
>
> //Magnus
>
> > -Original Message-
> > From: Dave Page [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, September 30, 2004 11:35 PM
> > To: [EMAIL PROTECTED]
>
M
> To: [EMAIL PROTECTED]
> Subject: [HACKERS] Libpq problem on Windows.
>
> I posted a message to pgsql-hackers-win32 regarding a problem
> with libpq exports on Win32 the other day, but have yet to
> receive any replies.
> Magnus & I have discussed the problem over IM a
I posted a message to pgsql-hackers-win32 regarding a problem with libpq
exports on Win32 the other day, but have yet to receive any replies.
Magnus & I have discussed the problem over IM and we both believe it is
important to fix, but neither of us are fluent enough in make-ese to do
so.
Basicall
Am Mittwoch, 11. August 2004 15:07 schrieb Andreas Pflug:
> Some recent change in libpq seems to interfere with gtk.
You could use "nm" to find common symbols that might be clashing. Besides
that, it's hard to tell more. Alternatively, compile with versioned symbols
and see whether the problem
Andreas Pflug wrote:
Some recent change in libpq seems to interfere with gtk.
After I tested a new pgadmin3 version on linuy yesterday, I found that
the GUI is hanging after PQconnectdb was called. After the call, the db
connection is fully functional, but the GUI mouse will show "waiting"
and t
Some recent change in libpq seems to interfere with gtk.
After I tested a new pgadmin3 version on linuy yesterday, I found that
the GUI is hanging after PQconnectdb was called. After the call, the db
connection is fully functional, but the GUI mouse will show "waiting"
and the program doesn't re