Re: proclock table corrupted

From: Harshitha S <hershetha(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: proclock table corrupted
Date: 2012-05-28 04:30:38
Message-ID: CAAe0G5vRFB5vK0L8g3Mk3v1JCf+tN6ponaU-bxn5ZjbrJDDUtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sorry, the OS is WindRiver Linux.
Yes , I am taking of the fast path locking patch discussed in the link
below.

http://postgresql.1045698.n5.nabble.com/bug-in-fast-path-locking-td5626629.html

Regards,
Harshitha

On Fri, May 25, 2012 at 7:09 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Harshitha S <hershetha(at)gmail(dot)com> writes:
> > We are encoutering the following error during normal operation of
> postgres.
> > postgres[10982]: [2-1] PANIC: proclock table corrupted
>
> Ugh. Can you provide a reproducible test case?
>
> > Version of Postgres : 9.0.3
> > Architecture : mips
> > OS: RedHat Linux
>
> [ raised eyebrow... ] I've been working at Red Hat for ten years, and
> I'm pretty sure they have never shipped a MIPS-based distro in that time.
> So what is that OS really?
>
> > Can you please let me know if 'fix-strong-lock-cleanup.patch' and this
> > error are related?
>
> This is not an adequate identification of what patch you are talking
> about; but if you are speaking of something related to Robert Haas'
> fast-path locking code, that's not in 9.0.x.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sandro Santilli 2012-05-28 06:48:21 Re: Interrupting long external library calls
Previous Message Karl Denninger 2012-05-28 04:14:52 Re: Attempting to do a rolling move to 9.2Beta (as a slave) fails