enterprisedb.com>]
> Sent: Tuesday, December 12, 2017 11:55 PM
> To: Duffey, Blake mailto:blake.duf...@noblis.org>>
> Cc:
> pgadmin-support@lists.postgresql.org<mailto:pgadmin-support@lists.postgresql.org>
> Subject: Re: pre-populate pgadmin4 configuration (server, for example)
<mailto:pgadmin-support@lists.postgresql.org>
Subject: Re: pre-populate pgadmin4 configuration (server, for example)
On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake
mailto:blake.duf...@noblis.org>> wrote:
pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’ certain
connect
>
> *From:* Murtuza Zabuawala [mailto:murtuza.zabuaw...@enterprisedb.com]
> *Sent:* Tuesday, December 12, 2017 11:55 PM
> *To:* Duffey, Blake
> *Cc:* pgadmin-support@lists.postgresql.org
> *Subject:* Re: pre-populate pgadmin4 configuration (server, for example)
>
>
>
> On Wed, Dec
@lists.postgresql.org
Subject: Re: pre-populate pgadmin4 configuration (server, for example)
On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake
mailto:blake.duf...@noblis.org>> wrote:
pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’ certain
connection entries (server, port, SS
On Wed, Dec 13, 2017 at 3:04 AM, Duffey, Blake
wrote:
> pgAdmin 3 leveraged registry keys that could be used to ‘pre-populate’
> certain connection entries (server, port, SSL, etc) for use cases such as
> terminal server/Citrix environments. In our (admittedly limited) testing
> pgAdmin 4 ver 2