That explains it... I thought it was a precent encoding but at the same
time a strange place for a control character.
Regards,
Ben Kim
On Mon, 8 Sep 2008, Alvaro Herrera wrote:
ERROR: invalid input syntax for type inet:
"fe80::104d:416e:a8dc:c02e%12"
SQL state: 22P02
Interesting.
Whe
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> ERROR: invalid input syntax for type inet:
> "fe80::104d:416e:a8dc:c02e%12"
>
> SQL state: 22P02
> Interesting.
> When we HAVE_IPV6, there's code to remove stuff after a % in an address.
We do now ... it wasn't there in 8.2.0.
http://archives.postg
>> ERROR: invalid input syntax for type inet:
>> "fe80::104d:416e:a8dc:c02e%12"
>>
>> SQL state: 22P02
Interesting.
When we HAVE_IPV6, there's code to remove stuff after a % in an address.
My bet is that what you're running was not compiled with HAVE_IPV6 and
so the code is not executed. Obvio
Sorry, I apologize for the mistake. %20 is the space, and the extra %12
seems to be DC3 (device control 3).
Regards,
Ben Kim
On Mon, 8 Sep 2008, Ben Kim wrote:
fe80::104d:416e:a8dc:c02e %12
Since %12 is a "space" character, it seems first thing to do might be an extra
space in your c
fe80::104d:416e:a8dc:c02e %12
Since %12 is a "space" character, it seems first thing to do might be an
extra space in your code. Just a quick guess.
Regards,
Ben Kim
On Mon, 8 Sep 2008, Sofer, Yuval wrote:
Hello,
postgres version: 8.2.0.4
platform windows: server 2008
I check co
Hello,
postgres version: 8.2.0.4
platform windows: server 2008
I check connections using:
SELECT pg_stat_get_backend_idset()
Now, I take the output and try to get the ip addresses using
select pg_stat_get_backend_client_addr();
but for a local connection (simple login us
