| 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-28 16:48:41 |
| Message-ID: | 7874.1338223721@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:
> Sorry, the OS is WindRiver Linux.
What I would suspect first is issues with the MIPS spinlock assembly
code (look into s_lock.h) not being portable to your platform. That
code hasn't been tested on very many machines, I suspect. It's not
impossible that it doesn't work at all on multiprocessor machines;
is yours one?
> 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
Not relevant to 9.0.x, for sure.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl Denninger | 2012-05-28 16:53:35 | Re: Attempting to do a rolling move to 9.2Beta (as a slave) fails |
| Previous Message | Tom Lane | 2012-05-28 16:44:52 | Re: Attempting to do a rolling move to 9.2Beta (as a slave) fails |