Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-performance-owner+M50699=pgsql-performance-ar@postgresql.org>)
 id 1VbeJ8-0004gV-0F
 for pgsql-performance@arkaria.postgresql.org; Wed, 30 Oct 2013 22:32:10 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-performance-owner+M50699=pgsql-performance-ar@postgresql.org>)
 id 1VbeJ7-0006OS-GZ
 for pgsql-performance@arkaria.postgresql.org; Wed, 30 Oct 2013 22:32:09 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <jnasby@enova.com>) id 1VbeJ6-0006OM-L3
 for pgsql-performance@postgresql.org; Wed, 30 Oct 2013 22:32:08 +0000
Received: from exprod5og116.obsmtp.com ([64.18.0.147])
 by makus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <jnasby@enova.com>) id 1VbeIy-0003Sn-5H
 for pgsql-performance@postgresql.org; Wed, 30 Oct 2013 22:32:06 +0000
Received: from mail-ie0-f179.google.com ([209.85.223.179]) (using TLSv1) by
 exprod5ob116.postini.com ([64.18.4.12]) with SMTP
 ID DSNKUnGI3xmt0I9/pq9S2MmrAc3YGuiEmuV5@postini.com;
 Wed, 30 Oct 2013 15:32:00 PDT
Received: by mail-ie0-f179.google.com with SMTP id aq17so3384385iec.24
 for <pgsql-performance@postgresql.org>; Wed, 30 Oct 2013 15:31:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enova.com; s=google;
 h=message-id:date:from:user-agent:mime-version:to:cc:subject
 :references:in-reply-to:content-type:content-transfer-encoding;
 bh=JTh68HzMmfjpuVK7YPEKmbZMx685BPD6NUrxsCkmp+I=;
 b=HrtmQUeB5cITe+YvWG71yUVpn2LuC621MDRv5CveuekWcx9eCdo8te589RkZJkj/LT
 ITLJu3HbzFWHSRICvpx6LpDQAwgORhmDvzi/tZxTIQxUFlz/OTabPemFo6/WPSaQU6Ok
 F7mhgHZeqKp1Y4s3uWTJngHWIWfFKU4Q0mE9Y=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
 :cc:subject:references:in-reply-to:content-type
 :content-transfer-encoding;
 bh=JTh68HzMmfjpuVK7YPEKmbZMx685BPD6NUrxsCkmp+I=;
 b=c8QBfjGxAjMMKm7276Toh2liC7V3X4+Lhyu6ng6xe9f/ffDUKxm5vQUWAy6JCaAznE
 wTelm8Lsw3mPdHKrLBUa7/ToLCCNPYzlKb8R3RmFfjRo7vuPOrjU0CUSUKMnGxyZkWKv
 nVsPzvTCp6KR5/HwQZdYHsiyujnMp7o7hJXHEWpjiSjdZ9B9DbbsxMuR0iM2/u4UFoiI
 NtY6RvtmxVrnPhqrOHFAAeLHwrtQ18p8lbzyrcv9euvT4NQEFyLQpE9u2KSizSOpI58E
 jmcJufcLXldnSTi+pGZnOYsxAjgHDTI4YQ1kDwGSzPbgI7bEIwAGCbjCmJHbr33kAioS
 1adQ==
X-Gm-Message-State: 
 ALoCoQl8F1Ui3odgHoFZKqK1FeEzlqY53IE4O7qlGdDtFWWIY2larc5h0VZ2bXwNc5IUZ7sg7aFeXtOMS3nYuo1ebD7YxdKqbnttspfX78FrkyiSG37KfivfvswOGQUCCngdt+oP1yy6PTRIH9TdPbiykhpW/xy/434unX3B9VOrRTeYmxL3d0VUeTMCcCr5uR27C48nyvwt
X-Received: by 10.43.151.205 with SMTP id kt13mr37748icc.70.1383172318732;
 Wed, 30 Oct 2013 15:31:58 -0700 (PDT)
X-Received: by 10.43.151.205 with SMTP id kt13mr37745icc.70.1383172318654;
 Wed, 30 Oct 2013 15:31:58 -0700 (PDT)
Received: from decina.local (rrcs-67-79-71-90.sw.biz.rr.com. [67.79.71.90])
 by mx.google.com with ESMTPSA id y10sm8810000igl.4.2013.10.30.15.31.56
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 30 Oct 2013 15:31:57 -0700 (PDT)
Message-ID: <527188E6.2030209@enova.com>
Date: Wed, 30 Oct 2013 17:32:06 -0500
From: Jim Nasby <jnasby@enova.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Merlin Moncure <mmoncure@gmail.com>,
 "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Problems with hash join over nested loop
References: <526EDDF7.3090102@enova.com> <13775.1383002035@sss.pgh.pa.us>
 <CAHyXU0ydScKt=-5G4yBpHWAh9eO6eV60P6uVCnui+YS9EMY5vw@mail.gmail.com>
 <526FE086.4020903@enova.com> <3692.1383065114@sss.pgh.pa.us>
 <526FE7D0.9000605@enova.com> <5575.1383070823@sss.pgh.pa.us>
 <527015BC.3020405@enova.com> <8314.1383078998@sss.pgh.pa.us>
 <527187ED.1000907@enova.com>
In-Reply-To: <527187ED.1000907@enova.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -4.3 (----)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 10/30/13 5:27 PM, Jim Nasby wrote:
> On 10/29/13 3:36 PM, Tom Lane wrote:
>> Jim Nasby <jnasby@enova.com> writes:
>>> Is there a way to measure memory consumption during planning, short of something like strace? (I've got no dev tools available on our servers.)
>>
>> Nothing built-in, I'm pretty sure.  You could probably add some
>> instrumentation, but that would require running modified executables ...
>
> FYI, client_min_messages = debug5 and log_planner_stats = on is useful, though I wish it included ru_maxrss (see http://www.gnu.org/software/libc/manual/html_node/Resource-Usage.html).

Oh, and in my 28 table case ru_minflt was 428 4k memory pages (1.7MB). Not a great measurement, but better than nothing. I didn't detect anything noticeable on vmstat either, so I don't think the consumption is huge (an email in the older thread mentioned 1GB... I'm not seeing that).
-- 
Jim Nasby, Lead Data Architect   (512) 569-9461


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance