From: | "Joshua Tolley" <eggyknap(at)gmail(dot)com> |
---|---|
To: | "manish singh" <manu_mani31(at)rediffmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4482: Segfault error 4 |
Date: | 2008-10-21 20:26:17 |
Message-ID: | e7e0a2570810211326v4ec5a47bk7e475a7934f37099@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Oct 16, 2008 at 10:33 AM, manish singh
<manu_mani31(at)rediffmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4482
> Logged by: manish singh
> Email address: manu_mani31(at)rediffmail(dot)com
> PostgreSQL version: 8.3
> Operating system: Centos 64bit
> Description: Segfault error 4
> Details:
>
> Database Postgressql 8.3.3 is on clustering and replication and is patched
> by pgcluster 1.9.rc5.patch
> now this time this below error getting.
>
> we are running this setup from last 1 year having no error, this error meet
> us this month OCT 2008
>
> kernel: postgres[4474]: segfault at 00002b21b5f92004 rip 0000000000536e10
> rsp 00007ffff80ec3c0 error 4
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>
If you're using pgcluster you'd do better reporting this to the
pgcluster mailing lists
- Josh / eggyknap
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-10-21 21:08:46 | Re: BUG #4478: = operator in connection with CASE looks like loose some functionality (bug or feature?) |
Previous Message | Marcel Petavy | 2008-10-21 11:58:40 | BUG #4488: jdbc : DatabaseMetaData.getPrimaryKeys no result |