| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Harshitha S <hershetha(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: proclock table corrupted |
| Date: | 2012-05-25 13:39:17 |
| Message-ID: | 19491.1337953157@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-05-25 13:49:18 | Re: [PATCH] Make skipped sort explicit in EXPLAIN ANALYZE |
| Previous Message | Marti Raudsepp | 2012-05-25 13:30:01 | [PATCH] Make skipped sort explicit in EXPLAIN ANALYZE |