From: | g(dot)vanluffelen(at)qipc(dot)com |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #8573: int4range memory consumption |
Date: | 2013-11-01 10:38:28 |
Message-ID: | E1VcC7Y-0006Tl-He@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
The following bug has been logged on the website:
Bug reference: 8573
Logged by: Godfried Vanluffelen
Email address: g(dot)vanluffelen(at)qipc(dot)com
PostgreSQL version: 9.3.1
Operating system: Windows 7 64 bit
Description:
int4range ( and any other range function) consumes much memory when used in
a select statement on a big table.
steps to reproduce:
-generate or use a table with 10M+ rows with 2 columns that are usable to
create a range. For example 1 column with negative numbers, and one with
positive numbers.
-invoke a simple select statement where you create a range of 2 columns. For
example select int4range(col1,col2) from table.
-memory builds up until the query is finished, or when out of memory error
occurs.
From | Date | Subject | |
---|---|---|---|
Next Message | Frank van Vugt | 2013-11-01 12:06:20 | Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion |
Previous Message | Kevin Grittner | 2013-11-01 08:20:50 | Re: [BUGS] BUG #8542: Materialized View with another column_name does not work? |
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2013-11-01 11:02:40 | Re: Show lossy heap block info in EXPLAIN ANALYZE for bitmap heap scan |
Previous Message | Mika Eloranta | 2013-11-01 09:42:30 | [PATCH] pg_receivexlog: fixed to work with logical segno > 0 |