John Hatfield <jhatfield@g-s.com.au> writes:
> (gdb) where
> #0 strcoll () at strcoll.c:248
> #1 0x8115b1f in lztext_cmp ()
> #2 0x8115b72 in lztext_eq ()
> #3 0x8098809 in vacuum ()
Hm. I suspect this is the same problem that a couple of other people
reported recently: crashes inside strcoll(), even though the strings
being passed to it are perfectly OK.
[ digs in archives... ] Dave Cramer reported a similar crash on
2001-01-24, and Jukka Honkela reported one on 2001-01-01. Dave was
also using 7.0.3, and Jukka current-as-of-then development sources.
Oh, this is interesting: all three of you are running RedHat 7.0!
I had originally assumed that Postgres was somehow clobbering strcoll's
internal locale information structures, but given that the problem is
only being reported on RH 7.0, a bug in strcoll itself is starting to
look like a plausible idea too.
Would one or another of you crank up ye olde debugger and try to figure
this out? If it is Postgres' fault, I want to fix it ... but it's hard
to do much when I can't reproduce the problem ...
regards, tom lane
