Backend cache invalidation initialization failed... HUH?

[Charset iso-8859-1 unsupported, filtering to ASCII...]

Here's the problem:

[rschutt@jin logs]$psql transfer
NOTICE: SIAssignBackendId: discarding tag 2147482551
Connection to database 'transfer' failed.
FATAL 1: Backend cache invalidation initialization failed

The frustrating thing is, psql seems to go thru phases where it will work
fine for a few minutes, and then it won't work at all for a few minutes,
then it will connect about 5% of the time for a while, and then it will
connect about 50% of the time.

Here's my config:
sparc SunOS 5.5.1, postgresql 6.3.2, apache 1.2.6 with mod_jserv, mod_php3,
and mod_perl compiled in (persistant mod_perl connections via Apache::DBI),
perl scripts accessing postgresql thru DBI, java servlets accessing
postgresql thru jdbc, and a few php pages.

It seems that all applications seem to connect or fail to connect to
postgresql with the same success rate.

Restarting apache seems to clear up the problem..

Any help would be greatly appreciated!!!

6.4 has better cache code, which I am sure will fix this.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

At 1:25 +0200 on 4/12/98, Bruce Momjian wrote:

6.4 has better cache code, which I am sure will fix this.

Don't be very sure... So far, I have not managed to successfully install
6.4 on my Solaris 2.5.1 (has very wierd regression results), and I saw
another complaint to the same effect (can't create database) from another
Solaris 2.5.1 user, who also claimed to have had problems with PG 6.3 (I
never got around to installing 6.3 so I wouldn't know). Now, this is the
third complaint about Solaris 2.5.1 which I see, and I have a bad feeling
some factor was introduced with 6.3, which broke Solaris 2.5.1
compatibility.

Which would mean that I'll have to say goodbye to Postgres, especially
since the mailing lists (I posted mine to this [GENERAL] list as well as
the ADMIN list and got no response of any kind).

It would be a real shame.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma

At 1:25 +0200 on 4/12/98, Bruce Momjian wrote:

6.4 has better cache code, which I am sure will fix this.

Don't be very sure... So far, I have not managed to successfully install
6.4 on my Solaris 2.5.1 (has very wierd regression results), and I saw
another complaint to the same effect (can't create database) from another
Solaris 2.5.1 user, who also claimed to have had problems with PG 6.3 (I
never got around to installing 6.3 so I wouldn't know). Now, this is the
third complaint about Solaris 2.5.1 which I see, and I have a bad feeling
some factor was introduced with 6.3, which broke Solaris 2.5.1
compatibility.

I don't even remember the problem.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

We are upgrading from 6.3.2 to 6.4 today on solaris 2.5.1. I'll let you
know how it goes..

-Ryan

-----Original Message-----
From: Herouth Maoz <herouth@oumail.openu.ac.il>
To: Bruce Momjian <maillist@candle.pha.pa.us>
Cc: pgsql-general@postgreSQL.org <pgsql-general@postgreSQL.org>
Date: Sunday, December 06, 1998 9:10 AM
Subject: Re: [GENERAL] Backend cache invalidation initialization failed...
HUH?