Am Tuesday, 5. August 2008 schrieb korry:
Perhaps the --check-config option should take an (optional) file name?
That would allow you to validate a config file without having to copy
it into place first.
postgres --check-config=myFilenameGoesHere -D $PGDATA
There is already an
Peter Eisentraut [EMAIL PROTECTED] writes:
Am Tuesday, 5. August 2008 schrieb korry:
Perhaps the --check-config option should take an (optional) file name?
That would allow you to validate a config file without having to copy
it into place first.
postgres --check-config=myFilenameGoesHere
On Aug 5, 2008, at 4:07 PM, Simon Riggs wrote:
On Sun, 2008-08-03 at 10:36 +0200, Magnus Hagander wrote:
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
The good way to solve this would be to have independant command
line
utilities which check pg_hba.conf, pg_ident.conf and
korry wrote:
On Aug 5, 2008, at 4:07 PM, Simon Riggs wrote:
On Sun, 2008-08-03 at 10:36 +0200, Magnus Hagander wrote:
Tom Lane wrote:
Magnus Hagander [EMAIL PROTECTED] writes:
The good way to solve this would be to have independant command line
utilities which check pg_hba.conf,
