Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eCDZA-0007PT-5h for pgsql-performance@arkaria.postgresql.org; Tue, 07 Nov 2017 23:46:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1eCDZ9-0007IJ-7E for pgsql-performance@arkaria.postgresql.org; Tue, 07 Nov 2017 23:45:59 +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.84_2) (envelope-from ) id 1eCDZ8-0007H9-4h for pgsql-performance@postgresql.org; Tue, 07 Nov 2017 23:45:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eCDZ1-00088k-Kj for pgsql-performance@postgresql.org; Tue, 07 Nov 2017 23:45:56 +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 vA7NjlKc013707; Tue, 7 Nov 2017 18:45:47 -0500 From: Tom Lane To: =?UTF-8?Q?Ulf_Lohbr=C3=BCgge?= cc: Scott Marlowe , Andres Freund , "pgsql-performance@postgresql.org" Subject: Re: Slow execution of SET ROLE, SET search_path and RESET ROLE In-reply-to: References: <20171107151108.3jtmta4xrgmuyrqf@alap3.anarazel.de> <20171107194517.pabhi4czbtiasb2f@alap3.anarazel.de> Comments: In-reply-to =?UTF-8?Q?Ulf_Lohbr=C3=BCgge?= message dated "Wed, 08 Nov 2017 00:04:18 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13705.1510098347.1@sss.pgh.pa.us> Date: Tue, 07 Nov 2017 18:45:47 -0500 Message-ID: <13706.1510098347@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org =?UTF-8?Q?Ulf_Lohbr=C3=BCgge?= writes: > I just ran "check_postgres.pl --action=bloat" and got the following output: > ... > Looks fine, doesn't it? A possible explanation is that something is taking an exclusive lock on some system catalog and holding it for a second or two. If so, turning on log_lock_waits might provide some useful info. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance