Re: [BUGS] WIN32 Non Blocking

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Darko Prenosil <darko_prenosil(at)yahoo(dot)com>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [BUGS] WIN32 Non Blocking
Date: 2001-08-04 04:23:25
Message-ID: 200108040423.f744NPo26606@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-interfaces pgsql-patches


Do we have a fix for this? It is a WIN32/libpq/multibyte problem.

>
> > 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
>
>

--
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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2001-08-04 11:54:23 alloc error on multiple action-queries within a rule
Previous Message Lamar Owen 2001-08-04 03:14:15 Re: HELP! BUG? pg_dump mucks up grant/revoke

Browse pgsql-interfaces by date

  From Date Subject
Next Message Dave Page 2001-08-04 11:56:43 RE: ODBC driver installation error
Previous Message Mihai Gheorghiu 2001-08-03 21:43:07 Re: ODBC driver installation error

Browse pgsql-patches by date

  From Date Subject
Next Message Dave Page 2001-08-04 11:37:23 RE: Patch for Improved Syntax Error Reporting
Previous Message Bruce Momjian 2001-08-03 21:58:54 Re: [HACKERS] Small patch for Hurd