From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: PostgreSQL cannot be compiled on RISC-V |
Date: | 2016-11-20 20:21:56 |
Message-ID: | 5e50e6b0-077c-6f2c-e498-45861d8b6efc@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 11/20/2016 11:35 AM, Tom Lane wrote:
> 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.
err, yeah, thats what I meant, all right. typing on my first cup of
coffee, hah!
> 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.
ahh, yeah, I knew there was something like that, I just couldn't
remember what. I'm vaguely remembering someone on this list a year
or so ago who was upset that localhost was hard coded to 127.0.0.1
because he was trying to do something weirdly 'clever' with it.
--
john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | Sandeep Thakkar | 2016-11-21 07:07:14 | Re: BUG #14425: Installation issues |
Previous Message | Richard W.M. Jones | 2016-11-20 19:54:00 | Re: PostgreSQL cannot be compiled on RISC-V |