Re: pg_getnameinfo_all() failed: Temporary failure in name resolution
| От | Adrian Klaver |
|---|---|
| Тема | Re: pg_getnameinfo_all() failed: Temporary failure in name resolution |
| Дата | |
| Msg-id | 7e79132a-0879-4382-823e-5a6b16d99dac@aklaver.com обсуждение исходный текст |
| Ответ на | pg_getnameinfo_all() failed: Temporary failure in name resolution (Ron Johnson <ronljohnsonjr@gmail.com>) |
| Ответы |
Re: pg_getnameinfo_all() failed: Temporary failure in name resolution
|
| Список | pgsql-general |
On 11/24/23 12:30, Ron Johnson wrote: > PG 9.6.24 (Yes, I know it's EOL.) > > I'm seeing lots of these in the postgresql log file: > 2023-11-24 15:09:02.224 EST [unknown] [unknown] > 18163 [unknown] 01000 WARNING: 01000: > pg_getnameinfo_all() failed: Temporary failure in name resolution > 2023-11-24 15:09:02.224 EST [unknown] [unknown] > 18163 [unknown] 01000 LOCATION: BackendInitialize, > postmaster.c:4220 > > What name is postgresql failing to resolve? From ~/src/common/ip.c /* * pg_getnameinfo_all - get name info for Unix, IPv4 and IPv6 sockets * * The API of this routine differs from the standard getnameinfo() definition * in two ways: first, the addr parameter is declared as sockaddr_storage * rather than struct sockaddr, and second, the node and service fields are * guaranteed to be filled with something even on failure return. */ -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: