Re: Alpha4 release blockers (was Re: wrapping up this CommitFest) - Mailing list pgsql-hackers

On Sat, Mar 05, 2011 at 11:46:13AM -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On Saturday 05 March 2011 04:44:20 Robert Haas wrote:
> >>> * Collation-related regression failure on buildfarm member pika.  This
> >>> is clearly a bug we need to identify, but maybe we can ship the alpha
> >>> without a fix --- for one thing, getting more than one report of the
> >>> problem would be helpful.
> 
> > I have just yesterday hit the same bug while testing some application on then 
> > HEAD, so its not just PIKA.
> 
> What platform, and what locale/encoding environment?

Hi,

i got the same issue using git head and managed to isolate a small testcase.

git head on debian/sid x86_64, gcc45

Reproducible with:

bin/initdb -D data/ --encoding=UTF-8 --locale=en_US
bin/postgres -B16384 -D data/ -p 5555 -h localhost

create database test with encoding='UTF8'

create table ad_window (ad_client_id varchar(32) not null , name varchar(60) not null, ad_module_id varchar(32) not
null);
create UNIQUE INDEX ad_window_name on ad_window(ad_client_id, name, ad_module_id);
insert into ad_window values ('0','Tables and Columns','0');
insert into ad_window values ('0','Reference','0');


The second insert fails consistently with:

WARNING:  text_cmp 1-1-<0'Tables and Columns0>-<0Reference0>
WARNING:  called from varlena: <0'Tables and Columns0> <0Reference0> for collid: (null)
ERROR:  locale operation to be invoked, but no collation was derived

The added elogs show the compared values on the second insert which first pointed me to the unique index as the
probabletrigger.
 

Backtrace of the failing text_cmp (not sure if useful):

#1  0x000000000077054b in bttextcmp (fcinfo=0x7fffbc1f9980) at varlena.c:1595
#2  0x00000000007cade4 in FunctionCall2 (flinfo=0x254e7b8, arg1=140410956296568, arg2=39118720) at fmgr.c:1387
#3  0x0000000000492330 in _bt_compare ()
#4  0x0000000000491e6a in _bt_binsrch ()
#5  0x000000000048a381 in _bt_doinsert ()
#6  0x000000000049077d in btinsert ()
#7  0x00000000007cb230 in FunctionCall6 (flinfo=0x247bc60, arg1=140411111761456, arg2=140736349578208,
arg3=140736349578176,   arg4=39118460, arg5=140411111755632, arg6=1) at fmgr.c:1500
 
#8  0x0000000000488ef0 in index_insert (indexRelation=0x7fb402706630, values=0x7fffbc1fa3e0, isnull=0x7fffbc1fa3c0 "",
 heap_t_ctid=0x254e67c, heapRelation=0x7fb402704f70, checkUnique=UNIQUE_CHECK_YES) at indexam.c:205
 
#9  0x00000000005cce68 in ExecInsertIndexTuples ()
#10 0x00000000005ddafc in ExecInsert ()
#11 0x00000000005de9e1 in ExecModifyTable ()
#12 0x00000000005c032a in ExecProcNode ()
#13 0x00000000005be204 in ExecutePlan ()
#14 0x00000000005bcabe in standard_ExecutorRun ()
#15 0x00000000005bc9b2 in ExecutorRun ()
#16 0x00000000006d2d9b in ProcessQuery (plan=0x2527350,    sourceText=0x245ebd0 "insert into ad_window values
('0','Reference','0');",params=0x0, dest=0x2527430,    completionTag=0x7fffbc1faa30 "") at pquery.c:187
 

Regards,
Stefan