pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: Robert Burgholzer <rburghol@vt.edu>
Cc: Burgholzer, Robert (DEQ) <Robert.Burgholzer@deq.virginia.gov>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: diagnosing a db crash - server exit code 2
Date: Tue, 04 Oct 2011 12:41:38 -0700
Message-ID: <4E8B6172.3000904@joeconway.com> (raw)
In-Reply-To: <CACT-NGK7AVLydPGLbPufZVd8ef54sNpTsByVP_UV4aEnUCBs1A@mail.gmail.com>
References: <B6C40D17104BEF47B1CB85623CDFAC6357BE26@COVMSGCES-EMB13.cov.virginia.gov>
	<4E7CDCA6.6060803@joeconway.com>
	<B6C40D17104BEF47B1CB85623CDFAC6357BE27@COVMSGCES-EMB13.cov.virginia.gov>
	<CAOR=d=3BoU+CRsOLVWY7a870cdQ2uc9KQcBA43cT-5J1_CKhow@mail.gmail.com>
	<B6C40D17104BEF47B1CB85623CDFAC6357BE2A@COVMSGCES-EMB13.cov.virginia.gov>
	<4E7CF42E.2050904@joeconway.com>
	<B6C40D17104BEF47B1CB85623CDFAC6357BE2F@COVMSGCES-EMB13.cov.virginia.gov>
	<CACT-NGKP07Ku5y7=JdOFDx+PYv-5w70CAv=N8yuc4w2HeSotHQ@mail.gmail.com>
	<4E84AB05.1050106@joeconway.com>
	<B6C40D17104BEF47B1CB85623CDFAC6302DD473B@COVMSGCES-EMB13.cov.virginia.gov>
	<CACT-NGJNW92jOFfp9N4u9APrmV0WjnJwg1ix37-yESWWSCDO2g@mail.gmail.com>
	<4E89F0CF.9080807@joeconway.com>
	<CACT-NGK7AVLydPGLbPufZVd8ef54sNpTsByVP_UV4aEnUCBs1A@mail.gmail.com>

On 10/04/2011 12:29 PM, Robert Burgholzer wrote:
> So, now I am starting to think that I did something erroneous when
> restarting the PG server, because after the most recent crash on my dev
> server, it is now seemingly uncrashable.  Which makes me think it is
> FIXED by the upgrade to 0.13 - which is awesome.  Though I was pretty
> certain that I had restarted the PG process - but it is possible that I
> missed it of course.

Are you pre-loading plr?

> FWIW, I used the following command:
>    pg_ctl -D /var/lib/pgsql/data restart -l logfile
> 
> I have run the test query 1,000 times in a loop on my dev server without
> a crash now, and it managed to crash the live server in a test after
> about 20 invocations earlier today.
> 
> So, thanks to everyone, I will chalk this up as a great learning
> experience, I have managed to get my stack traces and so forth, so that
> is awesome.  Your patience and willingness to help has been awesome.

Sounds good -- let us know if the problem resurfaces.

Joe

-- 
Joe Conway
credativ LLC: http://www.credativ.us
Linux, PostgreSQL, and general Open Source
Training, Service, Consulting, & 24x7 Support



view thread (24+ messages)

Message-ID: <4E8B6172.3000904@joeconway.com>
Permalink:  ../4E8B6172.3000904@joeconway.com/
Also on:    postgresql.org/message-id/4E8B6172.3000904@joeconway.com

 · 

reply
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-admin@postgresql.org
  Cc: mail@joeconway.com, rburghol@vt.edu, Robert.Burgholzer@deq.virginia.gov, scott.marlowe@gmail.com
  Subject: Re: diagnosing a db crash - server exit code 2
  In-Reply-To: <4E8B6172.3000904@joeconway.com>

* 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