Re: BUG #8013: Memory leak - Mailing list pgsql-bugs

From ajmcello
Subject Re: BUG #8013: Memory leak
Date
Msg-id CANuED-O=3rF1puFBGoHN0RQ4mhbfzJvVBBzufBXy113X6cgSbg@mail.gmail.com
Whole thread Raw
In response to BUG #8013: Memory leak  (stiening@comcast.net)
Responses Re: BUG #8013: Memory leak
List pgsql-bugs
unsubscribe


On Sat, Mar 30, 2013 at 7:01 AM, <stiening@comcast.net> wrote:

> 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(*) !=1 ORDER BY
> pts_key
>
> Which is executed as:
>  GroupAggregate  (cost=108680937.80..119278286.60 rows=470993280 width=4)
>    Filter: (count(*) <> 1)
>    ->  Sort  (cost=108680937.80..109858421.00 rows=470993280 width=4)
>          Sort Key: pts_key
>          ->  Seq Scan on tm_tm_pairs  (cost=0.00..8634876.80 rows=470993280
> width=4)
>
> 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='-O3 -march=native' ./configure --with-segsize=128
>
>
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

pgsql-bugs by date:

Previous
From: stiening@comcast.net
Date:
Subject: BUG #8013: Memory leak
Next
From: ajmcello
Date:
Subject: Re: Completely broken replica after PANIC: WAL contains references to invalid pages