pgadmin3 won't use IPv6

Bug #374656 reported by Neil Bertram
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pgadmin3 (Debian)
Fix Released
Unknown
pgadmin3 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: pgadmin3

When adding a new server in pgadmin3 that has no IPv4 address, I get the error:

An error has occurred:

Could not resolve hostname db.deor

It also doesn't accept the literal IPv6 address, complaining it can't resolve it.

I guess it just needs some IPv6 resolver/socket code, as the PostgreSQL client/server stuff is all perfectly v6-aware.

This is version 1.8.4-3, from Jaunty.

Tags: ipv6
Revision history for this message
Guillaume Lelarge (guillaume-lelarge-info) wrote :

Fixed upstream. Will be available in 1.12.

Changed in pgadmin3 (Debian):
status: Unknown → Confirmed
Changed in pgadmin3 (Debian):
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package pgadmin3 - 1.12.1-1

---------------
pgadmin3 (1.12.1-1) experimental; urgency=low

  * New upstream release.
  * Removed BSD file reference from copyright file, the whole text is in there
    anyway.

pgadmin3 (1.12.0-1) experimental; urgency=low

  * New upstream release candidate, containing fixes for:
    - won't use IPv6-only server (closes: #576342, LP: #374656)
    - All files should be "*", not "*." (closes: #594593)
  * Fixed watchfile to not consider -rc versions higher than non-rc
    versions (thanks to Michael Fladischer)
 -- Gerfried Fuchs <email address hidden> Fri, 29 Oct 2010 16:42:25 +0000

Changed in pgadmin3 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.