Re: WIN32 Non Blocking

From: "Darko Prenosil" <darko_prenosil(at)yahoo(dot)com>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: WIN32 Non Blocking
Date: 2001-07-21 19:56:19
Message-ID: 000701c1121f$3908f8e0$1700a8c0@darko
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-interfaces pgsql-patches


> I think we are in great shape now. Thanks. The elog() problem was
> because they didn't define FRONTEND in the compile.
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026

I start to dig little bit further and tried to compile WIN32 with MULTIBYTE
support.
There are also a few simple problems.
In src/include/miscadmin.h there is declared external function GetUserName.

Under WIN32 there is already declared that function in winbase.h

Description from MSDN:

BOOL GetUserName(
LPTSTR lpBuffer, // address of name buffer
LPDWORD nSize // address of size of name buffer
);
The GetUserName function retrieves the user name of the current thread. This
is the name of the user currently logged onto the system.

Fortunately Compiler reports error because function arguments are not the
same.
These two functions are not the same at all !!!
I think that this header should not be imported in libpq at all, or should
be
imported only some parts, I'm not for shore yet.
Just to make it work I only disabled GetUserName using WIN32 compiler
constant.
Is there maybe some other compiler constant that means that we are compiling
client library, or should I use FRONTEND compiler constant ?

Compilation after this, and few corrections in win32.h and win32.mak passed
ok,
but now I have another problem. When I tried to test libpq.dll by setting
client encoding, I end up with this error message from server :

"Client Encoding LATIN1 is not supported !"

I think that my server is compiled without MULTIBYTE, because it also
reports error
when I try to CREATE DATABASE WITH ENCODING.
Should I be shamed to confess that I do not know how to re-compile under
Linux ?
So, I first must read the installation manuals or wait for our "Linux-Man"
that returns to work in Monday !

However I'll send you a note as soon as some testing is done !

Darko(dot)Prenosil(at)finteh(dot)hr

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2001-07-21 21:01:02 When inserting '\' the insert fails.
Previous Message Tom Lane 2001-07-20 22:26:10 Re: Documentation Bug related to Inheritance

Browse pgsql-interfaces by date

  From Date Subject
Next Message Tatsuo Ishii 2001-07-22 11:10:32 Re: libpgtcl doesn't use UTF encoding of TCL
Previous Message edp 2001-07-20 21:44:33 How to get id of newly inserted row with DBD?

Browse pgsql-patches by date

  From Date Subject
Next Message Anders Bengtsson 2001-07-21 20:20:39 Re: [PATCHES] Re: [PATCH] Cleanup of JDBC character encoding
Previous Message Bruce Momjian 2001-07-21 18:52:22 Re: [PATCHES] Re: [PATCH] Cleanup of JDBC character encoding