Re: pg_hba changes not honored - Mailing list pgsql-admin

From Tom Lane
Subject Re: pg_hba changes not honored
Date
Msg-id 25784.1156376342@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_hba changes not honored  ("Sriram Dandapani" <sdandapani@counterpane.com>)
Responses Re: pg_hba changes not honored  ("Aaron Bono" <postgresql@aranya.com>)
List pgsql-admin
"Sriram Dandapani" <sdandapani@counterpane.com> writes:
> Pg_ctl is pointing to the same directory that postmaster points to on
> startup. There is only 1 data directory/postgres installation that I
> use.

> Pg_ctl informs that postmaster is signaled. When I see the logs for
> postmaster, it says "received SIGHUP, reloading configuration files"

Well, I just re-tested it here, and it works fine for me (using 8.1.4,
but I don't see anything in the CVS logs indicating changes in the
relevant code since 8.1.2).  So I still think there's some sort of
pilot error involved here, but I'm running out of ideas about what.
You might want to try the strace experiment I suggested to confirm
that the postmaster is reading the file you think it is.

            regards, tom lane

pgsql-admin by date:

Previous
From: "Sriram Dandapani"
Date:
Subject: Re: pg_hba changes not honored
Next
From: "Subbiah, Stalin"
Date:
Subject: Re: [PERFORM] Query tuning