Skip site navigation (1) Skip section navigation (2)

Re: Vacuum analyze problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Hatfield <jhatfield(at)g-s(dot)com(dot)au>
Cc: Jukka Honkela <fatal(at)ees2(dot)oulu(dot)fi>, Dave Cramer <Dave(at)micro-automation(dot)net>, pgsql-admin(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Vacuum analyze problem
Date: 2001-03-02 03:25:02
Message-ID: 1335.983503502@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-bugs
John Hatfield <jhatfield(at)g-s(dot)com(dot)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

In response to

pgsql-admin by date

Next:From: Johan SegernasDate: 2001-03-02 13:01:05
Subject: RE: COPY doesn't works when containing ' ' or ' ' characters on db
Previous:From: John HatfieldDate: 2001-03-02 02:49:25
Subject: RE: Vacuum analyze problem

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2001-03-02 08:29:20
Subject: Timestamp field error value
Previous:From: John HatfieldDate: 2001-03-02 02:49:25
Subject: RE: Vacuum analyze problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group