| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming Replication on win32 |
| Date: | 2010-01-22 11:34:26 |
| Message-ID: | 4B598D42.1050803@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marko Kreen wrote:
> On 1/22/10, Dimitri Fontaine <dfontaine(at)hi-media(dot)com> wrote:
>> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-01-22 11:39:05 | Re: Access to dynamic SQL in PL/pgSQL |
| Previous Message | Simon Riggs | 2010-01-22 11:00:35 | Re: Access to dynamic SQL in PL/pgSQL |