From: Chadwick Horn <chadhorn@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: postgres server crashes unexpectedly
Date: Tue, 18 Mar 2008 08:48:47 -0700
Message-ID: <8ECADC453D394D089097C660876A9BA7@ToshibaLaptop> (raw)
In-Reply-To: <25824.1205854526@sss.pgh.pa.us>
References: <71EB10BF787341C28A47F33667D0D8FC@ToshibaLaptop>
<7206.1205807551@sss.pgh.pa.us>
<785A9529D52A4C9891401C6DD0A22F24@ToshibaLaptop>
<25824.1205854526@sss.pgh.pa.us>
> "Chadwick Horn" <chadhorn@gmail.com> 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 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
> background --- it'd likely think psql is interactive and the postmaster
> isn't.
Is there a way to disable this or to make both interactive and/or
background?
>
>> What could be doing this? It just started out of the blue... I reindexed
>> the
>> index it mentioned and it seems to error out more...
>
> If you reindexed only the last-mentioned index, then you reindexed the
> wrong thing; it presumably died on the next index of story_member.
> I'd reindex the whole table rather than guess which that is.
>
> You should also consider the not-zero probability that you have more
> than one corrupted index. Keep reindexing tables until you can get
> through a database-wide VACUUM.
I have VACUUM'd it until it's fibers are coming out. It seems to crash at
various places (which, most likely, would be resolved if question #1 above
is possible) and holds no consistancy. The error logs provide even fewer
clues than the verbose output.
-chadwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: chadhorn@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: postgres server crashes unexpectedly
In-Reply-To: <8ECADC453D394D089097C660876A9BA7@ToshibaLaptop>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox