| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andrew Chernow <ac(at)esilo(dot)com> |
| Cc: | James Mansion <james(at)mansionfamily(dot)plus(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: libpq WSACleanup is not needed |
| Date: | 2009-01-19 19:32:46 |
| Message-ID: | 200901191932.n0JJWkI19667@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Chernow wrote:
> Bruce Momjian wrote:
> >
> > We could have gone with a more elegant init/uninit solution but there is
> > a history of slow upstream adoption of libpq API changes.
> >
> >
>
> If that's the case, adding a connectdb option seems like a good
> alternative. Orignally suggested here:
>
> http://archives.postgresql.org/pgsql-hackers/2009-01/msg01358.php
Right, well the big question is how many people are going to use the
connection option vs. doing it for everyone automatically.
One possible approach might be to do it automatically, and allow a
connection option to disable the WSACleanup() call.
Actually, right now, if you have two libpq connections, and close one,
does WSACleanup() get called, and does it affect the existing
connection?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2009-01-19 20:13:34 | Re: foreign_data test fails with non-C locale |
| Previous Message | Andrew Chernow | 2009-01-19 19:29:25 | Re: libpq WSACleanup is not needed |