Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 9966764FCCF for ; Thu, 18 Sep 2008 15:44:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 86729-03 for ; Thu, 18 Sep 2008 15:44:33 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by postgresql.org (Postfix) with ESMTP id 557C264FCBF for ; Thu, 18 Sep 2008 15:44:33 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n4so34944wag.5 for ; Thu, 18 Sep 2008 11:44:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=37DDjY5QMOWU5uYky016ZiiaPzHvSdOJF6xXiwELIyM=; b=FsU2bBgY84ebKyXMqCjFJQlt4wbNgqNgemJ1ZS/nvmJC1ehE3QL8IdUMFajraKg/mg l3iH5uQIxCxxjNg2+XS7CLm+hMkzJd+wWbXALdzCbJ0+BMytpgyRL3U50oBsobeF8TBU SyY7tYueOFC7z+NSF9QSF+/vB4H0iII8cfsMs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=G87RdEHGKW0K7krJs1r9Z0nMyyXHGGp16Z2Y+n34ni8QtPL4rBWR2FEqIeoVk0kOTc w1YK5iOTds+OqnrPDkJlMjzkW8N/xP2FVjZZ4E+8WNHmRGuhUdpY4FdrDIkNhDqZZa7G PxiQM7zFmHKPC86KhyyUFymLuD5c2TANaKAB8= Received: by 10.114.56.1 with SMTP id e1mr4288880waa.69.1221763467811; Thu, 18 Sep 2008 11:44:27 -0700 (PDT) Received: by 10.114.120.19 with HTTP; Thu, 18 Sep 2008 11:44:27 -0700 (PDT) Message-ID: Date: Thu, 18 Sep 2008 14:44:27 -0400 From: "Nikolas Everett" To: "Tom Lane" Subject: Re: Why does this query write to the disk? Cc: "Kevin Grittner" , pgsql-performance@postgresql.org In-Reply-To: <23587.1221761600@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25272_32199559.1221763467805" References: <48D24E6C.EE98.0025.0@wicourts.gov> <23587.1221761600@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200809/184 X-Sequence-Number: 31497 ------=_Part_25272_32199559.1221763467805 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline "Kevin Grittner" writes: > http://wiki.postgresql.org/wiki/Hint_Bits On Thu, Sep 18, 2008 at 2:13 PM, Tom Lane wrote: > freezing old tuples hash join was spilling out to temp files > Since this was a new table and the writes to the table's disk were very large it was probably the hint bits. The small table was about 1300 rows and my work_mem was 100MB so the writes to the main disk probably was not hash spillage. They were tiny, so I'm not worried about them. Thanks very much, Nik ------=_Part_25272_32199559.1221763467805 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> http://wiki.postgresql.org/wiki/Hint_Bits


On Thu, Sep 18, 2008 at 2:13 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
freezing old tuples 
hash join was spilling out to temp files

Since this was a new table and the writes to the table's disk were very large it was probably the hint bits.

The small table was about 1300 rows and my work_mem was 100MB so the writes to the main disk probably was not hash spillage.  They were tiny, so I'm not worried about  them.

Thanks very much,
Nik
------=_Part_25272_32199559.1221763467805--