Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fROaw-0001C9-RR for pgsql-general@arkaria.postgresql.org; Fri, 08 Jun 2018 21:06:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fROav-00009D-OZ for pgsql-general@arkaria.postgresql.org; Fri, 08 Jun 2018 21:06:49 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fROav-000090-1B; Fri, 08 Jun 2018 21:06:49 +0000 Received: from bay.acenet.us ([173.230.252.50]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fROas-000641-Ar; Fri, 08 Jun 2018 21:06:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VJb1IWAO2B4WO6t0Cf9xAKyO6MT6k58ZtyNo3kLLpmg=; b=n5RFd8iW/4+z6l8kV4KeaTk/Kx 1n31uCXB2OcOCnUJJvKP89MkvzdyDaHwc7ksXgPsrbTQvmUrOw+URTAeYfnucB3PQEOu60tqA6Chw hA3FZM+bBcsOhal/NPCTqQ0E+5QOiOGdeote5BGvhpE+447hkiK+8+3d7ahd2cndTqgkGfZ3QCKne 8A6UeqjkKZxHCW/U3AGm+rYHc1ccrgIX9z+vg+MhxSr30gXfX/iEJiQA7MuBYk/XeVBQb8KED/V88 3KYtEyP1e7IhhsDBguAkZznB85AOUmIgW7W1MGlEcrSBwVzbyPLuE+oPaHT+T86EX8zeMpBgssZ31 C8JDsz1w==; Received: from cos-128-210-107-26.science.purdue.edu ([128.210.107.26]:29094 helo=gibbs.math.purdue.edu) by bay.acenet.us with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1fROaq-000jc5-2m; Fri, 08 Jun 2018 17:06:44 -0400 Subject: Re: Performance problem postgresql 9.5 To: Miguel Angel Sanchez Sandoval , pgsql-admin@lists.postgresql.org, pgsql-general@lists.postgresql.org References: From: Chapman Flack Message-ID: <40bd111e-ba2a-d69d-ba29-80ee90960f7a@anastigmatix.net> Date: Fri, 8 Jun 2018 17:06:43 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-99.7 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap+anastigmatix.net/only user confirmed/virtual account not confirmed X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 06/08/2018 03:56 PM, Miguel Angel Sanchez Sandoval wrote: > I see the querys active and encounter > select fun ('./ 2yhdgrfrt63788') Would it be possible (observing appropriate precautions for a compromised server) to report here the language and definition of any function(s) named 'fun' in that database? Effectively: select lanname, prosrc, probin from pg_proc join pg_language as l on l.oid = prolang where proname = 'fun'; Regards, -Chap