Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 4DB962E0078 for ; Wed, 4 Jun 2008 12:10:15 -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 42498-07 for ; Wed, 4 Jun 2008 12:10:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id 7FF942E0073 for ; Wed, 4 Jun 2008 12:10:09 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m54FA8Rv024865; Wed, 4 Jun 2008 11:10:08 -0400 (EDT) To: Lewis Kapell cc: pgsql-performance@postgresql.org Subject: Re: backend pid changing In-reply-to: <4846AA49.5010601@setonhome.org> References: <4846AA49.5010601@setonhome.org> Comments: In-reply-to Lewis Kapell message dated "Wed, 04 Jun 2008 10:44:25 -0400" Date: Wed, 04 Jun 2008 11:10:08 -0400 Message-ID: <24864.1212592208@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/22 X-Sequence-Number: 30372 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