Re: Redefining inet_net_ntop - Mailing list pgsql-hackers

From Emre Hasegeli
Subject Re: Redefining inet_net_ntop
Date
Msg-id CAE2gYzx9XENk2aiJ10RPZkCnoyrVZTcwKkcD2=pgwRZ5ZJUPSw@mail.gmail.com
Whole thread Raw
In response to Redefining inet_net_ntop  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Redefining inet_net_ntop
List pgsql-hackers
> port.h declares inet_net_ntop and we always compile our own from
> port/inet_net_ntop.c .

There is another copy of it under backend/utils/adt/inet_cidr_ntop.c.
The code looks different but does 90% the same thing.  Their naming
and usage is confusing.

I recently needed to format IP addresses as DNS PTR records in the
database, and got annoyed by having no functions that outputs IPv6
addresses in easily parseable format like
0000:0000:0000:0000:0000:0000:0000:0000.  I was going to send a patch
to unify those C functions and add another SQL function to get
addresses in such format.  Is this a good plan?  Where should those C
functions be on the tree if they are not port of anything anymore?


pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: JIT compiling with LLVM v9.0
Next
From: "Tels"
Date:
Subject: Re: STATISTICS retained in CREATE TABLE ... LIKE (INCLUDING ALL)?