From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Wierd panic with 7.4.7 |
Date: | 2005-06-28 17:41:43 |
Message-ID: | 42C18BD7.5080206@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-28 17:54:17 | Re: [PATCHES] Users/Groups -> Roles |
Previous Message | Stephen Frost | 2005-06-28 17:30:25 | Re: CVS tip build failure (win32) |