From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <stark(at)mit(dot)edu> |
Cc: | "Richard W(dot)M(dot) Jones" <rjones(at)redhat(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL cannot be compiled on RISC-V |
Date: | 2016-11-20 19:35:42 |
Message-ID: | 10660.1479670542@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Greg Stark <stark(at)mit(dot)edu> writes:
> On Nov 20, 2016 6:57 PM, "John R Pierce" <pierce(at)hogranch(dot)com> wrote:
>> 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.
Right, we would need either UNIX-domain or TCP sockets for server
connections to work at all.
> I don't think we require tcp whether loopback or not.
We require UDP packet loopback to work for the stats collector to work.
If it weren't working, certain regression tests would probably fail,
and definitely the "stats" test would fail. Richard's last message
shows that as having passed.
So I think his kernel must have more networking ability than he
supposes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-11-20 19:45:18 | Re: PostgreSQL cannot be compiled on RISC-V |
Previous Message | Greg Stark | 2016-11-20 19:09:40 | Re: PostgreSQL cannot be compiled on RISC-V |