| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Japin Li <japinli(at)hotmail(dot)com> |
| Cc: | 大坏蛋！ <769323213(at)qq(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: error: #error PostgreSQL does not have native spinlock support on this platform. error: unknown type name ‘slock_t’ |
| Date: | 2022-09-17 14:51:27 |
| Message-ID: | 71597.1663426287@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Japin Li <japinli(at)hotmail(dot)com> writes:
> IIRC, PostgreSQL do not support loongarch platform, so if you want to
> use PostgreSQL on loongarch, you can a) disable spinlock when executing
> configure (not recommended for production) or b) implement a spinlock
> for PostgreSQL on loongarch64 platform.
Wikipedia suggests that loongarch is more or less a MIPS clone,
so maybe you could adapt the MIPS stanza in s_lock.h to work.
Do "make check" in src/backend/storage/lmgr for a basic smoke-test
of new spinlock code.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-09-19 14:28:23 | BUG #17618: unnecessary filter column <> text even after adding index |
| Previous Message | Japin Li | 2022-09-17 12:44:56 | Re: error: #error PostgreSQL does not have native spinlock support on this platform. error: unknown type name ‘slock_t’ |