BUG #8013: Memory leak

The following bug has been logged on the website:

Bug reference:      8013
Logged by:          Rae Stiening
Email address:      stiening@comcast.net
PostgreSQL version: 9.2.3
Operating system:   Suse Linux 9.3
Description:        =


The query:
SELECT pts_key,count(*)
         FROM tm_tm_pairs GROUP BY pts_key HAVING count(*) !=3D1 ORDER BY
pts_key

Which is executed as:
 GroupAggregate  (cost=3D108680937.80..119278286.60 rows=3D470993280 width=
=3D4)
   Filter: (count(*) <> 1)
   ->  Sort  (cost=3D108680937.80..109858421.00 rows=3D470993280 width=3D4)
         Sort Key: pts_key
         ->  Seq Scan on tm_tm_pairs  (cost=3D0.00..8634876.80 rows=3D47099=
3280
width=3D4)

uses all available memory (32GB).  pts_key is an integer and the table
contains about 500 million rows.

PostgreSQL 9.2.3 on x86_64-unknown-linux-gnu, compiled by gcc (SUSE Linux)
4.7.2 20130108 [gcc-4_7-branch revision 195012], 64-bit
(

compile options:

env CFLAGS=3D'-O3 -march=3Dnative' ./configure --with-segsize=3D128