Re: [BUGS] Postgresql 8.4.1 segfault, backtrace

2009-09-24 Thread Michael Brown
Tom Lane said: > "Michael Brown" writes: >> I have put in place a temporary workaround on the production system, >> which is to insert a > >> // Pretend that the cache is always invalid >> fprintf ( stderr, "*** bypassing cache ***\n" )

Re: [BUGS] Postgresql 8.4.1 segfault, backtrace

2009-09-24 Thread Michael Brown
Tom Lane said: > I shall go and do some further investigation, but at least it's now > clear where to look. Thanks for the report, and for being so helpful in > providing information! Thank you! I have put in place a temporary workaround on the production system, which is to insert a //

Re: [BUGS] Postgresql 8.4.1 segfault, backtrace

2009-09-24 Thread Michael Brown
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 n