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

Re: Postgresql 8.4.1 segfault, backtrace

From: Michael Brown <mbrown(at)fensystems(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Richard Neill <rn214(at)hermes(dot)cam(dot)ac(dot)uk>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgresql 8.4.1 segfault, backtrace
Date: 2009-09-24 22:07:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Thursday 24 September 2009 23:02:15 Michael Brown wrote:
> > I think this must mean that corrupt data is being read from the relcache
> > init file.  The reason a restart fixes it is probably that restart
> > forcibly removes the old init file, which is good for recovery but not
> > so good for finding out what's wrong.  Could you modify
> > RelationCacheInitFileRemove (at the bottom of relcache.c) to rename the
> >  file someplace else instead of deleting it?  And then send me a copy
> > of the bad file once you have one?
> I have captured and attached the file as saved-pg_internal.init.bak.

In case it helps, I noticed the following in gdb:

  (gdb) p *(RelIdCacheEnt*)status.curEntry
  $1 = {reloid = 932863600, reldesc = 0x0}

and this reloid is too high to be realistic; we have only just hit the two 
million mark for oids in pg_class.  This seems to support your thought that 
the relcache init file is corrupt.


pgsql-bugs by date

Next:From: Tom LaneDate: 2009-09-24 23:00:54
Subject: Re: Postgresql 8.4.1 segfault, backtrace
Previous:From: Russell SmithDate: 2009-09-24 21:54:36
Subject: Re: BUG #5063: MS Access crashes by quiting after linking tables with PostgreSQL

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