Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Joe Conway wrote:
>> OK, so now I see why we want this fixed for dblink and walreceiver, but
>> doesn't this approach leave every other WIN32 libpq client out in the
>> cold? Is there nothing that can be done for the general case, or is it a
> 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.
In response to
pgsql-hackers by date
|Next:||From: Marko Kreen||Date: 2010-01-22 10:28:29|
|Subject: Re: Streaming Replication on win32|
|Previous:||From: Huda Booley (firstname.lastname@example.org)||Date: 2010-01-22 08:42:33|
|Subject: Standby server lagging behind|