Re: libpq WSACleanup is not needed

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, James Mansion <james(at)mansionfamily(dot)plus(dot)com>, Jeroen Vermeulen <jtv(at)xs4all(dot)nl>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq WSACleanup is not needed
Date: 2009-01-22 16:54:37
Message-ID: 4978A4CD.5090509@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Chernow <ac(at)esilo(dot)com> writes:
>> I can try. Where should this be documented? ISTM that the best place
>> is at the top of "30.1 Database Connection Control Functions", since the
>> issue pertains to any connect/disconnect function. Does that sound
>> correct? Should it be a warning or just regular text?
>
> Minor platform-specific performance nits are not that important. Think
> "footnote", not "warning at the top of the page".
>
> regards, tom lane
>
>

Its a footnote at the end of the first paragraph in 30.1.

--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/

Attachment Content-Type Size
wsa.patch text/plain 2.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Chernow 2009-01-22 17:15:14 Re: libpq WSACleanup is not needed
Previous Message Robert Haas 2009-01-22 16:51:34 Re: Pluggable Indexes (was Re: rmgr hooks (v2))