Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id CDD212E0072 for ; Wed, 4 Jun 2008 12:18:44 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51048-05 for ; Wed, 4 Jun 2008 12:18:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from jonah.home.setonhome.org (mail.setonhome.org [65.213.207.11]) by developer.postgresql.org (Postfix) with ESMTP id 4EB0C2E0037 for ; Wed, 4 Jun 2008 12:18:41 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by jonah.home.setonhome.org (Postfix) with ESMTP id 41D946CC46D for ; Wed, 4 Jun 2008 11:15:34 -0400 (EDT) Received: from jonah.home.setonhome.org ([127.0.0.1]) by localhost (jonah.home.setonhome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gf4Ea0Rfvnc0; Wed, 4 Jun 2008 11:15:28 -0400 (EDT) Received: from [65.213.207.12] (unknown [65.213.207.12]) by jonah.home.setonhome.org (Postfix) with ESMTP id 658356CC482 for ; Wed, 4 Jun 2008 11:15:22 -0400 (EDT) Message-ID: <4846B244.7020307@setonhome.org> Date: Wed, 04 Jun 2008 11:18:28 -0400 From: Lewis Kapell Organization: Seton Home Study School User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: backend pid changing References: <4846AA49.5010601@setonhome.org> <24864.1212592208@sss.pgh.pa.us> In-Reply-To: <24864.1212592208@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=AWL=0.000 X-Spam-Level: X-Archive-Number: 200806/24 X-Sequence-Number: 30374 We are not using connection pooling, however the clients are tunneling through SSH. Forgot to mention that in my first message. Does that make any difference to it? Thank you, Lewis Kapell Computer Operations Seton Home Study School Tom Lane wrote: > Lewis Kapell writes: >> ... By examining the logs, I have observed that the >> backend pid for a particular client sometimes changes during a session. > > That is just about impossible to believe, unless perhaps you have a > connection pooler in the loop somewhere? > > regards, tom lane