Julius Tuskenis wrote: > Hello, list > > from the postgresql documentation I know, that "The pg_hba.conf file > is read on start-up and when the main server process receives a > SIGHUP signal. If you edit the file on an active system, you will > need to signal the server (using pg_ctl reload or kill -HUP) to make > it re-read the file." > > But there have been an incident this Saturday that indicates, that > these are not the only triggers for reading pg_hba.conf. One of our > clients edited pg_hba.conf that day (not correctly I must add), but > neither restarted nor reloaded the postgresql (logs below confirm > that). Anyway at some point the system started using the newly > edited file causing some problems. What could cause the pg_hba.conf > to be read by postgresql ? Hmm, isn't the file read every time a backend starts on Windows? This would explain the problem if the file was edited between 13:56:45 and 13:57:38. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
