X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 09DF99FC6A4 for ; Sun, 27 Aug 2006 15:58:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 06963-06 for ; Sun, 27 Aug 2006 18:58:27 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by postgresql.org (Postfix) with ESMTP id C4A7E9FC614 for ; Sun, 27 Aug 2006 15:58:26 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id d80so2114559pyd for ; Sun, 27 Aug 2006 11:58:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=qD/CTQuaSA+o1aUQEFmn34h8G27996qdlRY9saxRnlo35+mS+4FFCuZflF2K5WyPQCUrt88y+p9bvOro7r9DR29N1Zna/bxcer/gLz7zf2cvh/loydIksO3dscOW3ONs+fhhqQB1snNiMwiK3up9yPXP0/BLTLBTzzgE1dYySwA= Received: by 10.35.87.8 with SMTP id p8mr10503248pyl; Sun, 27 Aug 2006 11:58:25 -0700 (PDT) Received: by 10.35.80.9 with HTTP; Sun, 27 Aug 2006 11:58:25 -0700 (PDT) Message-ID: Date: Sun, 27 Aug 2006 13:58:25 -0500 From: "Aaron Bono" To: "Tom Lane" Subject: Re: pg_hba changes not honored Cc: "Sriram Dandapani" , "Joshua D. Drake" , pgsql-admin@postgresql.org In-Reply-To: <25784.1156376342@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_207442_18661418.1156705105529" References: <6992E470F12A444BB787B5C937B9D4DF0574FF4B@ca-mail1.cis.local> <25784.1156376342@sss.pgh.pa.us> X-Google-Sender-Auth: c19d1778216da2ad X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.574 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, HTML_30_40, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/304 X-Sequence-Number: 22847 ------=_Part_207442_18661418.1156705105529 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 8/23/06, Tom Lane wrote: > > "Sriram Dandapani" 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 ================================================================== ------=_Part_207442_18661418.1156705105529 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 8/23/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"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
================================================================== ------=_Part_207442_18661418.1156705105529--