Re: Wierd panic with 7.4.7 - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Wierd panic with 7.4.7
Date
Msg-id 42C18BD7.5080206@commandprompt.com
Whole thread Raw
In response to Re: Wierd panic with 7.4.7  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> 
> There are a couple of big problems with this theory, though.  In the
> first place, there aren't any messages sent to the client during
> post-commit; unless possibly it's an error message due to a failure
> during post-commit, and that should have shown up in the server log.
> In the second place, we don't treat communication failures as ERRORs,
> so how did step 3 happen?
> 
> Do you know what the dead client was doing?

Unfortunately I don't. We didn't have PID logging turned on so I can't 
tell which process it was. The only thing I was told was,

"I am running a Full Vacuum, CRAP the server just died ;)"

>  Can you reproduce this?

Let me see if the client has a dev database we can try to reproduce with.

Sincerely,

Joshua D. Drake


> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq


-- 
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] Users/Groups -> Roles
Next
From: Stephen Frost
Date:
Subject: Re: CVS tip build failure (win32)