Re: Dead code in ps_status.c
| От | Thomas Munro |
|---|---|
| Тема | Re: Dead code in ps_status.c |
| Дата | |
| Msg-id | CA+hUKG+nM0JQPjn5SpWs9NwzQ7DMPP3NtuAFCtm5ubc1Ti3W5w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Dead code in ps_status.c (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Dead code in ps_status.c
|
| Список | pgsql-hackers |
On Fri, Feb 17, 2023 at 3:38 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Thomas Munro <thomas.munro@gmail.com> writes: > > On Thu, Feb 16, 2023 at 6:34 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > My GCC compile farm account seems to have expired, or something, so I > > couldn't check on wrasse's host (though whether wrasse is "live" is > > debatable: Solaris 11.3 has reached EOL, it's just that the CPU is too > > old to be upgraded, so it's not testing a real OS that anyone would > > actually run PostgreSQL on). ... > My account still works, and what I see on wrasse's host is Just in case it helps someone else who finds themselves locked out of that, I noticed that I can still connect from my machine with OpenSSH 8.8p1, but not from another dev box which was upgraded to OpenSSH 9.2p1. For reasons I didn't look into, the latter doesn't like exchanging 1s and 0s with "Sun_SSH_2.4" (something Oracle has apparently now abandoned in favour of stock OpenSSH, but that machine is stuck in time).
В списке pgsql-hackers по дате отправления: