Re: current breakage with PGCLIENTENCODING

> Oh ... I'm an idiot. CVS tip isn't applying any encoding conversion
> to incoming query strings. I forgot a step in rearranging the handling
> of incoming messages :-(. Will fix shortly.

Ok.

BTW, I have digged into the problem which pg_client_encoding() returns
EUC_JP even psql starts up with PGCLIENTENCODING=SJIS. Weired thing is
when I created a fresh DB cluster pg_client_encoding() returns
SJIS. Of course both postgresql.conf are identical. I debugged with
gdb and found that the cause was SearchCatCacheList() could not get
the syscache entry for pg_conversion. Tom, do you have any idea for
this?

#0 SearchCatCacheList (cache=0x82a4198, nkeys=3, v1=2200, v2=28, v3=1, v4=0)
at catcache.c:1475
#1 0x0818d284 in SearchSysCacheList (cacheId=11, nkeys=3, key1=2200, key2=28,
key3=1, key4=0) at syscache.c:736
#2 0x0809e7a9 in FindDefaultConversion (name_space=2200, for_encoding=28,
to_encoding=1) at pg_conversion.c:215
#3 0x0809afa3 in FindDefaultConversionProc (for_encoding=28, to_encoding=1)
at namespace.c:1431
#4 0x0819ff47 in SetClientEncoding (encoding=28, doit=1 '\001')
at mbutils.c:83
#5 0x081a0085 in InitializeClientEncoding () at mbutils.c:135
#6 0x08195208 in InitPostgres (dbname=0x826d910 "test",
username=0x8267830 "t-ishii") at postinit.c:404
#7 0x081413fe in PostgresMain (argc=6, argv=0x82678c0,
username=0x8267830 "t-ishii") at postgres.c:1812
#8 0x08123eeb in DoBackend (port=0x8273978) at postmaster.c:2450
#9 0x08123737 in BackendStartup (port=0x8273978) at postmaster.c:2069
#10 0x081222fe in ServerLoop () at postmaster.c:1031
#11 0x08121e5e in PostmasterMain (argc=3, argv=0x8265d50) at postmaster.c:811
#12 0x080f9e9f in main (argc=3, argv=0xbffff7b4) at main.c:209
--
Tatsuo Ishii