Re: Postgresql 8.4.1 segfault, backtrace

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

    // Pretend that the cache is always invalid
    fprintf ( stderr, "*** bypassing cache ***\n" );
    goto read_failed;

immediately before

    /* check for correct magic number (compatible version) */
    if (fread(&magic, 1, sizeof(magic), fp) != sizeof(magic))
        goto read_failed;
    if (magic != RELCACHE_INIT_FILEMAGIC)
        goto read_failed;

in load_relcache_init_file().  This, I hope, will cause postgres to always
invalidate and rebuild the relcache init file.  The workaround has been in
place for around an hour so far and does not seem to be significantly
impacting upon performance.  If there is anything dangerous about this
workaround, could you let me know?

If you come up with a patch against 8.4.1, we should be able to test it
under production loads almost straight away.

Thanks again,

Michael