Thread: pgadmin Windows has no option to edit configuration files...
pgadmin Windows has no option to edit configuration files "C:\Program Files\PostgreSQL 10\data\pg_hba.conf" "C:\Program Files\PostgreSQL 10\data\postgresql.conf" i don't recommend doing this by hand, is it possible to add this option? André
pgadmin Windows has no option to edit configuration files
"C:\Program Files\PostgreSQL 10\data\pg_hba.conf"
"C:\Program Files\PostgreSQL 10\data\postgresql.conf"
i don't recommend doing this by hand, is it possible to add this option?
To my understanding pgAdmin is limited to communicating with PostgreSQL via a session - there is no guarantee that the two programs are even on the same machine. IOW, editing server boot configuration files seems outside of pgAdmin's charter. Administration of the contents of databases it what is targeted, not getting the server up and running in the first place. Configuration management tools cover the later.
I suppose it could wrap a UI on top of "ALTER SYSTEM"...
As of now there is no SQL-means to edit pg_hba.conf
You might need to accept that you are in the minority that those files should not be hand edited - ALTER SYSTEM provides for specialized usage but at the end of the day the desire for UI tools for those two (three: ident) files is pretty limited (at least relative to the cost to develop one).
David J.
PgAdminIII did/does have the facility to edit the postgresql.conf & pg_hba.conf.
However, as David G. Johnston pointed out, it was limited to editing _local_ versions
of those files.
>i don't recommend doing this by hand, ...
That statement implies that you feel that using a GUI will protect you from making
errors. That is untrue. If you use a GUI to change the authentication method in the
pg_hba.conf (not to mention other critical parameters), you could easily lock out
many users upon reloading/restart. Likewise, the same applies for changing values
in postgresql.conf. Simply having an easy way to change values does not mean you will
an easy way to do so.
However, as David G. Johnston pointed out, it was limited to editing _local_ versions
of those files.
>i don't recommend doing this by hand, ...
That statement implies that you feel that using a GUI will protect you from making
errors. That is untrue. If you use a GUI to change the authentication method in the
pg_hba.conf (not to mention other critical parameters), you could easily lock out
many users upon reloading/restart. Likewise, the same applies for changing values
in postgresql.conf. Simply having an easy way to change values does not mean you will
be protected from setting them too high(or wrong). EG: setting work_mem to 1GB will be
very bad.
It is better to learn and understand WHY you need to change values, than just havingan easy way to do so.
Melvin Davidson 🎸
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.![](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif)
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
![](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif)
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com
On Thursday, January 11, 2018, 4:49:47 PM EST, David G. Johnston <david.g.johnston@gmail.com> wrote:
pgadmin Windows has no option to edit configuration files
"C:\Program Files\PostgreSQL 10\data\pg_hba.conf"
"C:\Program Files\PostgreSQL 10\data\postgresql.conf"
i don't recommend doing this by hand, is it possible to add this option?
To my understanding pgAdmin is limited to communicating with PostgreSQL via a session - there is no guarantee that the two programs are even on the same machine. IOW, editing server boot configuration files seems outside of pgAdmin's charter. Administration of the contents of databases it what is targeted, not getting the server up and running in the first place. Configuration management tools cover the later.
I suppose it could wrap a UI on top of "ALTER SYSTEM"...
As of now there is no SQL-means to edit pg_hba.conf
You might need to accept that you are in the minority that those files should not be hand edited - ALTER SYSTEM provides for specialized usage but at the end of the day the desire for UI tools for those two (three: ident) files is pretty limited (at least relative to the cost to develop one).
David J.
On Thu, Jan 11, 2018 at 10:20 PM, Melvin Davidson <melvin6925@yahoo.com> wrote:
PgAdminIII did/does have the facility to edit the postgresql.conf & pg_hba.conf.
However, as David G. Johnston pointed out, it was limited to editing _local_ versions
of those files.
No it wasn't. There were separate menu options for remote editing...
>i don't recommend doing this by hand, ...
That statement implies that you feel that using a GUI will protect you from making
errors. That is untrue. If you use a GUI to change the authentication method in the
pg_hba.conf (not to mention other critical parameters), you could easily lock out
many users upon reloading/restart. Likewise, the same applies for changing values
in postgresql.conf. Simply having an easy way to change values does not mean you willbe protected from setting them too high(or wrong). EG: setting work_mem to 1GB will bevery bad.It is better to learn and understand WHY you need to change values, than just having
an easy way to do so.
...but you are otherwise correct - it was potentially dangerous and you could easily break a system doing it. It was also quite fragile, as it required the adminpack package which it used to completely re-write the config files, which had to be manually parsed and re-generated in order to (attempt) to keep any comments etc.
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company