| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Compiling on Termux |
| Date: | 2018-12-21 21:04:42 |
| Message-ID: | CAEepm=3oy2KqeniH=R=M4_Oe=hfmnw3SUNpLQGUGt_xn6ORr=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 22, 2018 at 7:32 AM David Fetter <david(at)fetter(dot)org> wrote:
> On Sat, Dec 22, 2018 at 07:03:32AM +1100, Thomas Munro wrote:
> > That talks about using -D__ANDROID_API__=23 (or presumably higher) to
> > make sure that sigtimedwait is exposed by signal.h. Something similar
> > may be afoot here.
>
> That worked perfectly...to expose the next issue, namely that at least
> part of the System-V IPC mechanisms have been left out. Do we support
> other systems where this is true?
Interesting, they left that stuff out deliberately out basically
because it all sucks:
PostgreSQL currently needs SysV shm just for the small segment that's
used for preventing multiple copies running in the same pgdata. You'd
need to find a new way to do that. We don't use SysV semaphores
(though we can) or message queues.
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2018-12-21 21:24:20 | Re: Compiling on Termux |
| Previous Message | David Fetter | 2018-12-21 20:32:17 | Re: Compiling on Termux |