Hi,
On Thu, 17 May 2007, Tom Lane wrote:
Christian Kratzer <[EMAIL PROTECTED]> writes:
It's not that simple though. The ipv6 stack will propably not allow
users to build sockets from addresses in link local scope from a
specific interface to a server bound to a global address, ::1
we hack the server to suppress any
%-foo found in the result of getnameinfo()?
Not sure what that would buy us. Stripping the scope from the address
does not seem the right thing to do.
Extending the generic inet type with scoped addresss is another question.
Greetings
Christian
--
Christian K
Hi,
On Thu, 17 May 2007, Andrew Sullivan wrote:
On Thu, May 17, 2007 at 07:29:47PM +0200, Christian Kratzer wrote:
supporting scoped addresses could have their uses but then again
theres nothing stopping you to bind multiple global ipv6 addresses
to your loopback interface which would work
Hi,
On Thu, 17 May 2007, Andrew Sullivan wrote:
On Thu, May 17, 2007 at 06:42:39PM +0200, Christian Kratzer wrote:
of a specific interface. This is why bsd based oprating systems append
%ifname to the address so that they know which Interface this address
Oh, I forgot about that wart in
r details.
There is propbaly not much point in using link local addreses for postgres.
You should have global ipv6 prefix on your interfaces to really make use
of ipv6.
Greetins
Christian
--
Christian Kratzer CK Software GmbH
Email: [EMAIL PROTECTED] S
D::Pg) if you have to pass
parameters in the SQL string to use partial indexes.
I hope you are not relying on prepared statements as your only
defense against sql code injection.
Greetings
Christian
--
Christian Kratzer [EMAIL PROTECTED]
CK Software GmbH
