Re: pg_getaddrinfo_all() with hintp=NULL
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Sergey Tatarintsev <s.tatarintsev@postgrespro.ru>,
"pgsql-hackers@lists.postgresql.org"
<pgsql-hackers@lists.postgresql.org>
Date: 2025-11-13T00:17:36Z
Lists: pgsql-hackers
Daniel Gustafsson <daniel@yesql.se> writes: > It's still not clear to ne that we should make pg_getaddr_info() mimic the API > of getaddrinfo since it's not a thin wrapper over getaddrinfo. The alternative > option would be to return EAI_FAIL on a null hint and force the caller to > provide an AF_UNSPEC if that is what is indeed asked for. We already reject null hints (by crashing), and have done for decades. I don't think there's anything very wrong with the current code, and I don't really see that the proposed patch is an improvement. If anything, I'd just add a comment to pg_getaddrinfo_all saying that unlike bare getaddrinfo, we require a valid hintp. regards, tom lane
Commits
-
Document that pg_getaddrinfo_all does not accept null hints
- d22cc7326ce0 19 (unreleased) landed