From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #312: Feature request: ability to set hostaddr |
Date: | 2011-03-12 09:36:55 |
Message-ID: | 057.74560461c196abf952cfab7d49468235@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#312: Feature request: ability to set hostaddr
------------------------------+---------------------------------------------
Reporter: Christopher Head | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: 1.12
Keywords: server | Platform: all
------------------------------+---------------------------------------------
I'd like to request the ability to set hostaddr separately from host when
creating a server connection. This is currently impossible. Alternatively,
allow pgAdmin3 to connect to services described in .pg_service.conf, thus
allowing a way to set all parameters that are not currently available in
the connection configuration UI.
Use case: "host" is set to the actual name of the database server so it
can fully verify an SSL certificate, "hostaddr" is set to the IP address
of some box acting as a tunnel without which a connection to the database
server is impossible. I'm sure there are others, but that's mine.
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/312>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2011-03-12 19:13:03 | Re: [pgadmin-hackers] Re: [pgadmin-hackers] error: expected initializer before ‘!’ token |
Previous Message | pgAdmin Trac | 2011-03-12 09:33:55 | [pgAdmin III] #311: SQL code blocks do not know about CASE..END |