Re: BUG #4113: server closed the connection unexpectedly
От | Alvaro Herrera |
---|---|
Тема | Re: BUG #4113: server closed the connection unexpectedly |
Дата | |
Msg-id | 20080421155353.GQ6520@alvh.no-ip.org обсуждение исходный текст |
Ответ на | BUG #4113: server closed the connection unexpectedly ("Javier Hernandez" <dba@loopone.com>) |
Ответы |
Re: BUG #4113: server closed the connection unexpectedly
|
Список | pgsql-bugs |
Javier Hernandez wrote: > select * from numeric_col_table where num_col in (select int_col from > int_col_table); #0 0x0000000000752368 in pg_detoast_datum (datum=0x1) at /pgsql/source/00head/src/backend/utils/fmgr/fmgr.c:2101 #1 0x00000000006bf8bc in hash_numeric (fcinfo=0x7fffc5140550) at /pgsql/source/00head/src/backend/utils/adt/numeric.c:1163 #2 0x000000000075081f in FunctionCall1 (flinfo=0xc65688, arg1=1) at /pgsql/source/00head/src/backend/utils/fmgr/fmgr.c:1250 #3 0x00000000005898c1 in TupleHashTableHash (key=0x7fffc51409f0, keysize=8) at /pgsql/source/00head/src/backend/executor/execGrouping.c:513 #4 0x00000000007550ee in hash_search (hashp=0xc6aec8, keyPtr=0x7fffc51409f0, action=HASH_ENTER, foundPtr=0x7fffc51409ef "") at /pgsql/source/00head/src/backend/utils/hash/dynahash.c:791 #5 0x0000000000589635 in LookupTupleHashEntry (hashtable=0xc68eb8, slot=0xc63078, isnew=0x7fffc5140a6f "") at /pgsql/source/00head/src/backend/executor/execGrouping.c:368 #6 0x000000000059e2e3 in lookup_hash_entry (aggstate=0xc64490, inputslot=0xc63138) at /pgsql/source/00head/src/backend/executor/nodeAgg.c:777 #7 0x000000000059e701 in agg_fill_hash_table (aggstate=0xc64490) at /pgsql/source/00head/src/backend/executor/nodeAgg.c:1028 #8 0x000000000059e35e in ExecAgg (node=0xc64490) at /pgsql/source/00head/src/backend/executor/nodeAgg.c:812 So what's happening here is that it's writing the hash table using the wrong datatype ... -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-bugs по дате отправления: