Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dRPo5-0005Yf-Bp for pgsql-performance@arkaria.postgresql.org; Sat, 01 Jul 2017 21:19:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dRPo4-0001ac-B0 for pgsql-performance@arkaria.postgresql.org; Sat, 01 Jul 2017 21:19:56 +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 1dRPmK-0006is-CE for pgsql-performance@postgresql.org; Sat, 01 Jul 2017 21:18:08 +0000 Received: from mimolette.dalibo.net ([212.85.157.144] helo=mail.dalibo.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dRPmG-0006cb-R4 for pgsql-performance@postgresql.org; Sat, 01 Jul 2017 21:18:06 +0000 Received: from nol.local (unknown [78.192.238.147]) by mail.dalibo.com (Postfix) with ESMTPSA id B5ECA2C04C2; Sat, 1 Jul 2017 23:18:01 +0200 (CEST) Subject: Re: Simple SQL too slow To: Tomas Vondra , Daviramos Roussenq Fortunato , pgsql-performance@postgresql.org References: <623C03A8-ABA5-4BF1-8225-348CF5E6848E@a-kretschmer.de> <7152357d-5cac-20d6-9c08-ea56878c3d03@2ndquadrant.com> From: Julien Rouhaud Message-ID: <81a45651-ebf9-0df2-5351-5aa71055a58f@dalibo.com> Date: Sat, 1 Jul 2017 23:17:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <7152357d-5cac-20d6-9c08-ea56878c3d03@2ndquadrant.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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 On 01/07/2017 22:58, Tomas Vondra wrote: > After that, you need to determine what is the bottleneck. Perhaps the > resources are saturated by something else running on the system - other > queries, maybe something else running next to PostgreSQL. Look at top > and iotop while running the queries, and other system tools. > Another explanation would be network issue. Are they stored in different locations? And dhoes EXPLAIN ANALYZE select * from MINHATABELA has similar timings on both environment? Also, I didn't see any indication about how exactly were the tests performed. Was it using psql, pgAdmin or something else ? -- Julien Rouhaud http://dalibo.com - http://dalibo.org -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance