B.,
I hate to be the bearer of bad news, but in a nutshell no. As you write,
with both pgAdmin and postgreSQL installed on the same machine there is no
need to open any ports to access that particular postgreSQL instance.
Unfortunately unless the other application is also installed on that same
s
I think you are missing the point Andrzej, my pgadmin and postgresql do run
on the same server and there is no need to open up port 5432 externally or
even internally and block access to the external world via the firewall as
pgadmin is connected via the local socket. And I like to keep it that way
But pgAdmin runs at the same ports, so You need them to be opened.
You can set in pgconf allowed IP pool.
You can change default port no por postgresql
Maybe You can consider "hardware" solution: on Your gateway make in
firewall rule for specific IP address with port mapping/triggering
e.g. If Yo
Andrzej,
QGIS is just an example as I use it in combination with postgis in order to
work in mapping GIS elements.
With odbc I still need to open up the server ports to the outside world
which is what I want to avoid.
regards,
Bastiaan
On Wed, 12 Aug 2020 at 11:43, androxkentaki wrote:
> i don
i don't know what id Qgis and why You want to do it via pgAdmin...
But did You consider using ODBC connection and its driver?
śr., 12 sie 2020 o 08:58 bw napisał(a):
> Hi,
>
> As I do not like to open-up my postgresql port to the outside world and
> managing users via pgadmin is very user frien
