Re: [HACKERS] VACUUM ANALYZE problem on linux
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] VACUUM ANALYZE problem on linux |
Дата | |
Msg-id | 13249.921511102@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] VACUUM ANALYZE problem on linux (Oleg Broytmann <phd@sun.med.ru>) |
Ответы |
Re: [HACKERS] VACUUM ANALYZE problem on linux
Re: [HACKERS] VACUUM ANALYZE problem on linux Re: [HACKERS] VACUUM ANALYZE problem on linux Re: [HACKERS] VACUUM ANALYZE problem on linux |
Список | pgsql-hackers |
Oleg Broytmann <phd@sun.med.ru> writes: > To remind of the problem - I have a problem running VACUUM ANALYZE on a > glibc2 linux (Debian 2.0). On solaris it is Ok (and I got a report it is Ok > on HP-UX). > Here is the traceback. The problem is in strcoll, don't understand why. > Program received signal SIGSEGV, Segmentation fault. > 0x40119587 in strcoll () > (gdb) where > #0 0x40119587 in strcoll () > #1 0x816cadd in varstr_cmp (arg1=0x4020fccc " ", len1=0, > arg2=0x8268604 " ", len2=0) at varlena.c:511 > #2 0x816b31d in bpcharlt (arg1=0x4020fcc8 "\n", arg2=0x8268600 "\n") > at varchar.c:504 Sure looks like strcoll is broken on your platform. Build a little test program and see if strcoll("", "") coredumps ... if the traceback is accurate, that's what was getting passed to it. BTW, why in the world is varstr_cmp written to duplicate the strings it's passed, rather than just handing them off to strcoll() as-is? regards, tom lane
В списке pgsql-hackers по дате отправления: