| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, James Mansion <james(at)mansionfamily(dot)plus(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: libpq WSACleanup is not needed |
| Date: | 2009-01-20 16:36:56 |
| Message-ID: | 4975FDA8.8040202@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Chernow wrote:
> Bruce Momjian wrote:
>>
>> Ah, OK, so it does its own cleanup on last close, great. I agree a
>> connection option for this would be good.
>>
>
> What would the option be? "wsainit = [enable | disable]"? Maybe it
> should allow setting the version to load: "wsa_version = 2.0". Maybe
> the two should be combined: "wsa_version = [default | disable | 2.0]".
>
I will say, the cleanest solution is still an optional init()/uninit()
for libpq. Has this been ruled out? IMHO, the next best solution is a
connection option.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-01-20 16:39:03 | Re: libpq WSACleanup is not needed |
| Previous Message | Andrew Chernow | 2009-01-20 16:31:31 | Re: libpq WSACleanup is not needed |