Heikki Linnakangas <heikki.linnakan...@enterprisedb.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 >> SMOP? > > 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. -- dim -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
