Re: Compiling libpq with VC6
От | Andreas Pflug |
---|---|
Тема | Re: Compiling libpq with VC6 |
Дата | |
Msg-id | 4123AEA9.4050005@pse-consulting.de обсуждение исходный текст |
Ответ на | Re: Compiling libpq with VC6 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Compiling libpq with VC6
Re: Compiling libpq with VC6 |
Список | pgsql-patches |
Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.us> writes: > >>Andreas Pflug wrote: >> >>>Not really. The backend will still use the reliable pg_ functions. >>>Frontends continue to use the libc functions, which are totally >>>sufficient in non-concurrent access situations. > > >>I would like to keep full Unix semantics for these functions even in >>libpq, if possible. > libpq doesn't use either rename or unlink AFAIK. However, if we make > the patch be something involving #ifdef FRONTEND, then it will affect > other code that might want to use those. > > One thing that hasn't been real clear to me is why this only affects > fe-lobj.c, when we have many other files that include <io.h> after > including postgres.h. Quite simple: mingw includes do *not* conflict. Only a minority of tools is object to VC6 compilation, ultimately only libpq is needed. Regards, Andreas
В списке pgsql-patches по дате отправления: