Hello Folks,
This may be a dumb question but please bear a moment with me.
About the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL commands,
assuming the settings are saved in an internal table, what would be the
need for
Gevik Babakhani wrote:
This may be a dumb question but please bear a moment with me.
About the TODO item “%Allow pg_hba.conf settings to be controlled via
SQL“: If in the future we could configure the settings by SQL commands,
assuming the settings are saved in an internal table, what would be
Gevik Babakhani schrieb:
Hello Folks,
This may be a dumb question but please bear a moment with me.
About the TODO item “%Allow pg_hba.conf settings to be controlled via
SQL“: If in the future we could configure the settings by SQL commands,
assuming the settings are saved in an internal table,
On Thursday 06 April 2006 09:45, Gevik Babakhani wrote:
Hello Folks,
This may be a dumb question but please bear a moment with me.
About the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL commands,
assuming the
I agree. Security is a good reason to have the pg_bha.conf around. I guess
it would make the TODO item a bit harder to develop hence one has to read
and write the file to support the future SQL commands too. I also looked
at the code for a moment; perhaps using a yacc/lex mechanism would make
[EMAIL PROTECTED] (Gevik Babakhani) writes:
This may be a dumb question but please bear a moment with me. About
the TODO item %Allow pg_hba.conf settings to be controlled via
SQL: If in the future we could configure the settings by SQL
commands, assuming the settings are saved in an internal
