If you launch your progress server at startup (in init.d), you only have to type : # service postgresql reload It works fine. Luc
----- Original Message ----- From: "Christopher Browne" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, July 31, 2004 3:09 AM Subject: Re: [GENERAL] pg_hba.conf changes without restarting postmaster > After a long battle with technology, [EMAIL PROTECTED] (Si Chen), an earthling, wrote: > > It seems that every time I make a change to pg_hba.conf, I have to > > restart the database server for the new authentication to take effect. > > Is there a way to have the server use the new pg_hba.conf > > authentication without restarting the production server. > > You NEVER need to restart the database server to reflect pg_hba.conf > changes. > > The command "pg_ctl -D $PGDATA reload" will cause the server to reload > the contents of pg_hba.conf, assuming PGDATA is appropriately set. > Several other methods are possible, all of which ultimately amount to > sending the signal SIGHUP to the postmaster. > -- > (format nil "[EMAIL PROTECTED]" "cbbrowne" "ntlug.org") > http://www3.sympatico.ca/cbbrowne/linux.html > I found out why cats drink out of the toilet. My mother told me it's > because it's cold in there. And I'm like: How did my mother know THAT? > --Wendy Liebman > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > > ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
