Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ipcr9-0007um-HV for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2020 18:48:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ipcr8-0002Pz-AW for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2020 18:48:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ipcr8-0002Ps-0s for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2020 18:48:30 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ipcr5-0004eJ-RY for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2020 18:48:29 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 009Im1vJ007043; Thu, 9 Jan 2020 13:48:01 -0500 From: Tom Lane To: Peter cc: pgsql-general@lists.postgresql.org Subject: Re: 12.1 not useable: clientlib fails after a dozen queries (GSSAPI ?) In-reply-to: <20200109181822.GA74698@gate.oper.dinoex.org> References: <20200109181822.GA74698@gate.oper.dinoex.org> Comments: In-reply-to Peter message dated "Thu, 09 Jan 2020 19:18:22 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7041.1578595681.1@sss.pgh.pa.us> Date: Thu, 09 Jan 2020 13:48:01 -0500 Message-ID: <7042.1578595681@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Peter writes: > with 12.1, after a couple of queries, at a random place, the clientlib > does produce a failed query without giving reason or error-message [1]. > Then when retrying, the clientlib switches off signal handling and > sits inactive in memory (needs kill -9). Seems like you'd better raise this with the author(s) of the "pg" Ruby gem. Perhaps they read this mailing list, but more likely they have a specific bug reporting mechanism somewhere. regards, tom lane