| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AIX 4.3 getaddrinfo busted |
| Date: | 2009-01-23 15:44:28 |
| Message-ID: | 4979E5DC.1090404@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Chernow <ac(at)esilo(dot)com> writes:
>> Bruce Momjian wrote:
>>> Why would we risk breaking other platforms to avoid an AIX bug? At best
>>> we can put a code comment in that section of the code.
>
>> IMO, there is no risk. getaddrinfo allows a NULL second argument on
>> every platform I have worked with.
>
> The portability risk is in the "manually set the port" part.
>
Right. If this method is limited to _AIX and only when the failure case
occurs, there are no portability issues. I've already confirmed my fix
works on 4.3 and 6.1. The buildfarm will tell us if 5.3 works (very
likely it will).
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-01-23 15:51:16 | Hot standby, conflict resolution |
| Previous Message | Tom Lane | 2009-01-23 15:38:14 | Re: problem with archive_command as suggested by documentation |