| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL cannot be compiled on RISC-V |
| Date: | 2016-11-20 19:09:40 |
| Message-ID: | CAM-w4HN+c16HkFMhPfcKQgzn=z1J3U9RwiSThsKZFPzG2YnTcg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Nov 20, 2016 6:57 PM, "John R Pierce" <pierce(at)hogranch(dot)com> wrote:
>
> On 11/20/2016 2:36 AM, Richard W.M. Jones wrote:
>>
>> This is *probably* because our kernel lacks networking support, but I
didn't look at this in great detail yet.
>
>
> wait, what?? postgres can't function at all without basic networking
support, including at least named pipes and tcp over localhost.
I think you mean the named UNIX domain socket in /tmp. Technically not the
same thing as named pipes.
I don't think we require tcp whether loopback or not. You can certainly
configure the server not to accept tcp at all and only the UNIX domain
connections which is presumably good enough if it's a kernel issue.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-11-20 19:35:42 | Re: PostgreSQL cannot be compiled on RISC-V |
| Previous Message | Richard W.M. Jones | 2016-11-20 19:08:27 | Re: PostgreSQL cannot be compiled on RISC-V |