I suspect the same behavior. Existing jdbc connections are not disconnected..only new ones
From: aaron.bono@gmail.com [mailto:aaron.bono@gmail.com] On Behalf Of Aaron Bono Sent: Sunday, August 27, 2006 11:58 AM To: Tom Lane Cc: Sriram Dandapani; Joshua D. Drake; pgsql-admin@postgresql.org Subject: Re: [ADMIN] pg_hba changes not honored
"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.
Could it be that the JDBC client creates a connection and keeps that connection open (common with connection poolilng)? If you SIGHUP the postmaster, will it disconnect already connected clients or does it only reject new connections?
I say this since you said doing a restart fixes the problem.
================================================================== Aaron Bono Aranya Software Technologies, Inc. http://www.aranya.com http://codeelixir.com ==================================================================