Marko Kreen wrote: > On 1/22/10, Dimitri Fontaine <dfonta...@hi-media.com> wrote: >> Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> writes: >> > The problem only applies to libpq calls from the backend. Client apps >> > are not affected, only backend modules. If there's any other modules out >> > there that use libpq, then yes, those have a problem too. >> >> >> plproxy comes to mind. > > Thats interesting. PL/Proxy deos not use PQexec, it uses async > execution and waits on sockets with plain select() called > from code compiled with backend headers. > > So it seems to be already using pgwin32_select(). Or not?
Yes. I just grepped plproxy source code and there's indeed no blocking libpq calls there. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
