Re: Cleaning up historical portability baggage
| От | Thomas Munro |
|---|---|
| Тема | Re: Cleaning up historical portability baggage |
| Дата | |
| Msg-id | CA+hUKGKvJk4r-_SFaOuU5_sk+Zd6JUkQyaqY_qfPRBmduTGh1w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Cleaning up historical portability baggage (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: Cleaning up historical portability baggage
|
| Список | pgsql-hackers |
On Tue, Aug 16, 2022 at 7:25 AM Andres Freund <andres@anarazel.de> wrote: > On 2022-08-15 13:48:22 +1200, Thomas Munro wrote: > > 2022-08-13 20:44:35.174 GMT [4760][postmaster] LOG: listening on Unix > > socket "@c:/cirrus/.s.PGSQL.61696" > > What I find odd is that you said your naive program rejected this... No, I said it wasn't behaving sanely. It allowed me to create two sockets and bind them both to "\000C:\\xxxxxxxxxx", but I expected the second to fail with EADDRINUSE/10048[1]. I was messing around with things like that because my original aim was to check if the names are silently truncated through EADDRINUSE errors, an approach that worked for regular Unix sockets. [1] https://cirrus-ci.com/task/4643322672185344?logs=main#L16
В списке pgsql-hackers по дате отправления: