| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Lars Ewald (web(dot)de)" <l(dot)ewald-web(at)lars-ewald(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Fwd: Re: Compile fails on AIX 6.1 |
| Date: | 2014-08-02 15:09:00 |
| Message-ID: | 2127.1406992140@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"Lars Ewald (web.de)" <l(dot)ewald-web(at)lars-ewald(dot)de> writes:
>> We don't really consider a platform
>> supported unless it's got working spinlocks.
> I am a little bit confused about that.
Well, so are we.
> Or is there a problem on the specific machine? Or is there something disabled
> in the kernel?
It seems to be a toolchain problem, ie, compiler or assembler doing
something unexpected with our PPC spinlock code. But we don't really
have enough info to diagnose. I can think of a bunch of ways it might
have gone wrong, but we seem to have eliminated all those theories :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry White | 2014-08-03 16:49:11 | Re: BUG #11109: No Toast compression on JSON, JSONB columns |
| Previous Message | Robert Fleming | 2014-08-01 19:55:07 | Re: BUG #11028: psql doesn't use 0x01 and 0x02 to inform readline of non-printable PROMPT1 chars |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Cochran | 2014-08-02 18:43:20 | Looked at TODO:Considering improving performance of computing CHAR() value lengths |
| Previous Message | Daniele Varrazzo | 2014-08-02 13:15:26 | Re: Fixed redundant i18n strings in json |