I suspect the same behavior. Existing jdbc connections are not
disconnected..only new ones
From: aaron(dot)bono(at)gmail(dot)com [mailto:aaron(dot)bono(at)gmail(dot)com] On Behalf Of
Sent: Sunday, August 27, 2006 11:58 AM
To: Tom Lane
Cc: Sriram Dandapani; Joshua D. Drake; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] pg_hba changes not honored
On 8/23/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
"Sriram Dandapani" <sdandapani(at)counterpane(dot)com> writes:
> Pg_ctl is pointing to the same directory that postmaster
points to on
> startup. There is only 1 data directory/postgres installation
> Pg_ctl informs that postmaster is signaled. When I see the
> postmaster, it says "received SIGHUP, reloading configuration
Well, I just re-tested it here, and it works fine for me (using
but I don't see anything in the CVS logs indicating changes in
relevant code since 8.1.2). So I still think there's some sort
pilot error involved here, but I'm running out of ideas about
You might want to try the strace experiment I suggested to
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.
Aranya Software Technologies, Inc.
pgsql-admin by date
|Next:||From: Enrique Arizón||Date: 2006-08-27 21:07:51|
|Subject: Advice request: Postgresql setup for flash memories.|
|Previous:||From: Aaron Bono||Date: 2006-08-27 18:58:25|
|Subject: Re: pg_hba changes not honored|