Nope im using 2.2.18 but ill recompile it to enable debug and return with
the error
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Ben-Nes Michael" <miki@canaan.co.il>
Cc: <pgsql-general@postgresql.org>
Sent: Friday, July 20, 2001 8:01 PM
Subject: Re: [GENERAL] VACUUM ANALYZE
> "Ben-Nes Michael" <miki@canaan.co.il> writes:
> > (gdb) bt
> > #0 0x4014d8e0 in ?? ()
> > #1 0x8123a52 in ?? ()
> > #2 0x8123a9f in ?? ()
> > #3 0x8123caa in ?? ()
> > [ etc ]
>
> Sigh, that's no help at all :-(. Looks like you are using a postgres
> executable that's been stripped of all symbolic information. Don't
> suppose you want to compile from source to make a more debuggable copy?
>
> Actually, maybe it's not quite no help at all. I'm going to guess from
> the numeric values that the core dump is occurring in a system library
> (since the top address is so far different from the rest). Since this
> is a vacuum analyze, and since it's on a redhat machine, I'm going to
> leap to a conclusion: maybe you are running into the known strcoll()
> bug. Are you running glibc earlier than 2.2.3? If so, an update to
> 2.2.3 may fix it. See the thread at
>
> http://fts.postgresql.org/db/mw/msg.html?mid=1021209
>
> regards, tom lane
>
--------------------------
Canaan Surfing Ltd.
Internet Service Providers
Ben-Nes Michael - Manager
Tel: 972-4-6991122
http://sites.canaan.co.il
--------------------------
