Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-performance-owner+M50698=pgsql-performance-ar@postgresql.org>)
 id 1VbeF7-0004IA-4F
 for pgsql-performance@arkaria.postgresql.org; Wed, 30 Oct 2013 22:28:01 +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+M50698=pgsql-performance-ar@postgresql.org>)
 id 1VbeF5-0004ZK-Pv
 for pgsql-performance@arkaria.postgresql.org; Wed, 30 Oct 2013 22:27:59 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <jnasby@enova.com>) id 1VbeF4-0004Z8-La
 for pgsql-performance@postgresql.org; Wed, 30 Oct 2013 22:27:58 +0000
Received: from exprod5og106.obsmtp.com ([64.18.0.182])
 by magus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <jnasby@enova.com>) id 1VbeEw-0004Cm-VL
 for pgsql-performance@postgresql.org; Wed, 30 Oct 2013 22:27:58 +0000
Received: from mail-ie0-f178.google.com ([209.85.223.178]) (using TLSv1) by
 exprod5ob106.postini.com ([64.18.4.12]) with SMTP
 ID DSNKUnGH5Vd4S/k7EI/eg+ZSiyHEisPZ+q+a@postini.com;
 Wed, 30 Oct 2013 15:27:50 PDT
Received: by mail-ie0-f178.google.com with SMTP id x13so3584920ief.9
 for <pgsql-performance@postgresql.org>; Wed, 30 Oct 2013 15:27:48 -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=kNQXcjm5ecY5WPKNtc8VztZLaMKEPwlZGQfxHTyttWQ=;
 b=SPNqEGKHk4UHq1ejosnRYNZ8kLh1gGmLdiWiq80W9gIs9b7gruYFcdVhHwKir08aBD
 OdjHFcAvsTeJp3QnHSaiOYC8CmGJ5EOfUUAoiFtv39PH47NWroCZxFBIiSymXB31MJa8
 F7AfHwHy3IxK3Hmzoj/9JA5oW/kxe4tgkn0a0=
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=kNQXcjm5ecY5WPKNtc8VztZLaMKEPwlZGQfxHTyttWQ=;
 b=UU2DDjWNXY/SMp8Eotwwx+pLncZgHxjvErqIhbt4BQmwq9BtN7NchowLq2kpaBa853
 7RCGY6IP2BUV2jyqY/6NPwSrMUeTNvJ+FVnQB7NFjwBNvJ9xbg78ZTSQsGibayaGh7eS
 2Y7uVnse6pPbq134AyS6wyhKzKEUvAQuMkOdHsU+eiTS2jg+vTpouESxlqc62WJlmRQL
 2pRpEReOgYB4qepzn1+E4Ztbw0DWkZdMBgNxEW9VDDQXzUBG1n2UfnmD6t1UejJwhqg/
 qB1X4gr4e3WWCZPwUtJWz/gst2vTx+80T7ZcStDoCQKrlc0ArYtgmsSXUss64Ypp9Meg
 dV8w==
X-Gm-Message-State: 
 ALoCoQmZidWh2VyK7KA074kwpojigTqT+PYqzkHUfrFfWci3mrh3xSoZxIrezFeSOcAAbqsVlGcMQwRc7nQAVI+Yhrwf20/7+z5eesAs1xHzP2yyOYBCYiMdIijK4iFfiY0KyiQoeB/8EsM2iWGkAdEmQN9cfkrCO2oXStWuOZGB1Yna/krQOtmmCI4jBgOgKabOFbHDfwU7
X-Received: by 10.50.109.132 with SMTP id hs4mr4259710igb.34.1383172068823;
 Wed, 30 Oct 2013 15:27:48 -0700 (PDT)
X-Received: by 10.50.109.132 with SMTP id hs4mr4259703igb.34.1383172068700;
 Wed, 30 Oct 2013 15:27:48 -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 cl4sm8881889igc.1.2013.10.30.15.27.47
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 30 Oct 2013 15:27:48 -0700 (PDT)
Message-ID: <527187ED.1000907@enova.com>
Date: Wed, 30 Oct 2013 17:27:57 -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>
In-Reply-To: <8314.1383078998@sss.pgh.pa.us>
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/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).
-- 
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