| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Andrew Chernow <ac(at)esilo(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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:41:42 |
| Message-ID: | 4975FEC6.5070707@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Chernow wrote:
> 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.
What happened to the idea of counting connections? That seemed a
relatively clean way to go, I thought, although I haven't followed the
discussion very closely.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-01-20 16:42:49 | Re: libpq WSACleanup is not needed |
| Previous Message | Bruce Momjian | 2009-01-20 16:39:03 | Re: libpq WSACleanup is not needed |