Re: [HACKERS] VACUUM ANALYZE problem on linux

Поиск
Список
Период
Сортировка
От Oleg Broytmann
Тема Re: [HACKERS] VACUUM ANALYZE problem on linux
Дата
Msg-id Pine.SOL2.3.96.SK.990315151816.23120A-100000@sun.med.ru
обсуждение исходный текст
Ответ на Re: [HACKERS] VACUUM ANALYZE problem on linux  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] VACUUM ANALYZE problem on linux  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hello!

On Thu, 11 Feb 1999, Tom Lane wrote:
> Could you build the backend with -g and send a gdb backtrace from the
> corefile produced when the crash occurs?
  I have a problem getting core - postgres didn't produces core. Recently
I got a suggestion (from Vadim) to attach gdb to a running process and
debug it this way. Ok, done.  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
#3  0x80a1bb7 in vc_attrstats (onerel=0x8264378, vacrelstats=0x8262a10,    tuple=0x4020fc90) at vacuum.c:1630
#4  0x809ffec in vc_scanheap (vacrelstats=0x8262a10, onerel=0x8264378,    vacuum_pages=0xbfffcf84,
fraged_pages=0xbfffcf78)at vacuum.c:806
 
#5  0x809f773 in vc_vacone (relid=32600, analyze=1 '\001', va_cols=0x0)   at vacuum.c:504
#6  0x809ed84 in vc_vacuum (VacRelP=0x0, analyze=1 '\001', va_cols=0x0)   at vacuum.c:257
#7  0x809ec3e in vacuum (vacrel=0x0, verbose=0 '\000', analyze=1 '\001',    va_spec=0x0) at vacuum.c:160
#8  0x8138c43 in ProcessUtility (parsetree=0x82464e0, dest=Remote)   at utility.c:644
#9  0x8135388 in pg_exec_query_dest (query_string=0xbfffd0d4 "vacuum
analyze;",    dest=Remote, aclOverride=0 '\000') at postgres.c:758
#10 0x8135264 in pg_exec_query (query_string=0xbfffd0d4 "vacuum analyze;")   at postgres.c:699
#11 0x813677e in PostgresMain (argc=6, argv=0xbffff15c, real_argc=8,    real_argv=0xbffffafc) at postgres.c:1645
#12 0x8111561 in DoBackend (port=0x82110f0) at postmaster.c:1541
#13 0x8110f35 in BackendStartup (port=0x82110f0) at postmaster.c:1312
#14 0x811012f in ServerLoop () at postmaster.c:757
#15 0x810fb5e in PostmasterMain (argc=8, argv=0xbffffafc) at
postmaster.c:563
#16 0x80c8c32 in main (argc=8, argv=0xbffffafc) at main.c:93

> 
>             regards, tom lane
> 

Oleg.
----    Oleg Broytmann     http://members.xoom.com/phd2/     phd2@earthling.net          Programmers don't die, they
justGOSUB without RETURN.
 



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Ryan Bradetich
Дата:
Сообщение: Sequences....
Следующее
От: "D'Arcy" "J.M." Cain
Дата:
Сообщение: Re: [HACKERS] ICQ?