current is broken - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject current is broken
Date
Msg-id 20000913130722A.t-ishii@sra.co.jp
Whole thread Raw
Responses Re: current is broken
Re: current is broken
List pgsql-hackers
It seems current source is broken if MB is enabled.

gcc -c  -I../../../src/interfaces/libpq -I../../../src/include  -I../../../src/interfaces/libpq -O2 -Wall
-Wmissing-prototypes-Wmissing-declarations pg_dump.c -o pg_dump.o
 
pg_dump.c: In function `isViewRule':
pg_dump.c:267: parse error before `int'
pg_dump.c:268: `len' undeclared (first use in this function)
pg_dump.c:268: (Each undeclared identifier is reported only once
pg_dump.c:268: for each function it appears in.)
pg_dump.c:268: warning: implicit declaration of function `pg_mbcliplen'
make[3]: *** [pg_dump.o] Error 1

The problem is:

#ifdef MULTIBYTEint len;len = pg_mbcliplen(rulename,strlen(rulename),NAMEDATALEN-1);rulename[len] = '\0';
#else::

Moreover, pg_mbcliplen cannot be used in frontend. It seems what we
need here is new backendside functiontion what does same as
pg_mbcliplen. Will look into this...
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Status of new relation file naming
Next
From: Philip Warner
Date:
Subject: Re: current is broken