From: | Prem Gopalan <prem(at)mazunetworks(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Postgres Crashes |
Date: | 2004-07-02 11:42:54 |
Message-ID: | Pine.LNX.4.44.0407020737340.1378-100000@mazu.mazunetworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
After reproducing these crashes and running tests long enough, we found
that these Postgres Crashes happen on linux 2.4.18 and not on linux
2.4.25. In all likelihood, this is a kernel (or driver) issue.
Could you kindly ensure this gets on my mail thread with subject "Postgres
Crashes".
Thanks
Prem.
On Wed, 5 May 2004, Tom Lane wrote:
> prem(at)mazunetworks(dot)com (Prem Gopalan) writes:
> > The dying process is postmaster. After these crashes the server is
> > missing from ps and no more new connections are possible. The backend
> > processes stay on till their connections close.
>
> That behavior does sound like a postmaster crash --- but all the stack
> traces you show are clearly in backend code. A backend crash ought not
> take out the postmaster. So something fairly odd is going on here.
>
> What if anything shows up in the postmaster's stderr log when this
> happens?
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2004-07-02 11:57:18 | Re: Adding column comment to information_schema.columns |
Previous Message | Thomas Hallgren | 2004-07-02 11:14:39 | Re: transactions within functions |