Chadwick Horn wrote:
It looks to me like psql is managing to start a new connection
before the postmaster notices the crash of the prior backend and
tells everybody to get out of town. Which is odd, but maybe not
too implausible if your kernel is set up to favor interactive
processes over ba
"Chadwick Horn" <[EMAIL PROTECTED]> writes:
I keep getting this error:
Attempting reset: WARNING: terminating connection because of crash of
another server process
It looks to me like psql is managing to start a new connection before
the postmaster notices the crash of the prior backend and
"Chadwick Horn" <[EMAIL PROTECTED]> writes:
> I keep getting this error:
> Attempting reset: WARNING: terminating connection because of crash of another
> server process
It looks to me like psql is managing to start a new connection before
the postmaster notices the crash of the prior backend an
TECTED]>
To: "Chadwick Horn" <[EMAIL PROTECTED]>
Cc: "Tom Lane" <[EMAIL PROTECTED]>;
Sent: Tuesday, March 18, 2008 8:37 AM
Subject: Re: [SQL] postgres server crashes unexpectedly
On Tue, 18 Mar 2008, Chadwick Horn wrote:
Sorry about the lack of information
On Tue, 18 Mar 2008, Chadwick Horn wrote:
Sorry about the lack of information on the system. We're running fedora (not
for sure what version though) core (whitebox).
This may not matter in the least bit, but have you tried running the DB on
a real RHEL, or CentOS box? The kernel and libs on
t;[EMAIL PROTECTED]>
To: "Chadwick Horn" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, March 17, 2008 7:32 PM
Subject: Re: [SQL] postgres server crashes unexpectedly
"Chadwick Horn" <[EMAIL PROTECTED]> writes:
PANIC: corrupted item pointer: offset = 0, size = 0
LOG:
"Chadwick Horn" <[EMAIL PROTECTED]> writes:
> PANIC: corrupted item pointer: offset = 0, size = 0
> LOG: autovacuum process (PID 3037) was terminated by signal 6
Hmm ... the only instances of that error text are in PageIndexTupleDelete
and PageIndexMultiDelete, so we can fairly safely say that y
hi all,
we've had a db to stop working for some reason and have searched through google
to it's ends to no avail. we have reindexed the database and system database as
tried to determine other things that would keep it from working... again, to no
avail.
this just started occuring about 2 week
