From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Robert Burgholzer <rburghol(at)vt(dot)edu> |
Cc: | "Burgholzer, Robert (DEQ)" <Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: diagnosing a db crash - server exit code 2 |
Date: | 2011-10-04 19:41:38 |
Message-ID: | 4E8B6172.3000904@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-10-05 05:51:33 | Re: streaming replication and wraparound vacuuming |
Previous Message | Robert Burgholzer | 2011-10-04 19:29:21 | Re: diagnosing a db crash - server exit code 2 |