| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | close() vs. closesocket() |
| Date: | 2003-04-24 18:35:02 |
| Message-ID: | 200304241835.h3OIZ2s04294@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Looking at libpq, you can see Win32 requires closesocket() while Unix
uses just uses close().
I have to add this type of change to the backend for Win32, so I am
inclined to make all the socket close calls closesocket() and #define
that as close() on Unix? It would remove quite a few Win32 defs from
libpq too.
Comments?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Dyas | 2003-04-24 18:36:41 | Re: query optimization scenarios 17,701 times faster!!! |
| Previous Message | Alice Lottini | 2003-04-24 18:19:00 | table creation using backend functions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-04-25 01:20:03 | Re: [HACKERS] close() vs. closesocket() |
| Previous Message | Philip Yarra | 2003-04-24 00:24:25 | Re: ECPG thread-safety |