Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XJ6QR-0000Ss-O6 for pgsql-sql@arkaria.postgresql.org; Sun, 17 Aug 2014 19:47:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XJ6QQ-0001Wn-2p for pgsql-sql@arkaria.postgresql.org; Sun, 17 Aug 2014 19:47:34 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XJ6QN-0001We-SS for pgsql-sql@postgresql.org; Sun, 17 Aug 2014 19:47:32 +0000 Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XJ6QK-0001pE-7v for pgsql-sql@postgresql.org; Sun, 17 Aug 2014 19:47:29 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XJ6QI-0005Zj-Gm for pgsql-sql@postgresql.org; Sun, 17 Aug 2014 12:47:26 -0700 Date: Sun, 17 Aug 2014 12:47:26 -0700 (PDT) From: gmb To: pgsql-sql@postgresql.org Message-ID: <1408304846514-5815126.post@n5.nabble.com> In-Reply-To: <1408272021571-5815111.post@n5.nabble.com> References: <1408260946918-5815108.post@n5.nabble.com> <1408272021571-5815111.post@n5.nabble.com> Subject: Re: High memory usage / performance issue ( temp tables ? ) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 2.7 (++) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org Something else I intended to ask in the original post, but forgot: What effect , if any , will the autovacuum setting have in this type of scenario ? Will performance be improved by disabling this ? I assume that a vacuum process will be required on at least the pg_catalog due to dropping of temp tables during the process. Regards gmb -- View this message in context: http://postgresql.1045698.n5.nabble.com/High-memory-usage-performance-issue-temp-tables-tp5815108p5815126.html Sent from the PostgreSQL - sql mailing list archive at Nabble.com. -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql