On Jun 22, 2006, at 4:02 PM, Relyea, Mike wrote:
Thanks Jim and Tom. At least now I've got a direction to head in. I
think for now I'll probably reduce work_mem as a stop-gap measure
to get
the query running again. This will buy me some time to redesign it.
I'll probably separate out each s
Thanks Jim and Tom. At least now I've got a direction to head in. I
think for now I'll probably reduce work_mem as a stop-gap measure to get
the query running again. This will buy me some time to redesign it.
I'll probably separate out each sub query and store the results in a
table (would a tem
Tom Lane wrote:
Hmm. One of the things that's on my TODO list is to make the planner
smarter about drilling down into sub-selects to extract statistics.
I think that's what's called for here, but your example has eliminated
all the interesting details. Can you show us the actual query, its
EXP
On Jun 22, 2006, at 2:23 PM, Tom Lane wrote:
"Relyea, Mike" <[EMAIL PROTECTED]> writes:
I've zipped the results of EXPLAIN INSERT INTO "tblSummary" SELECT *
FROM "qrySummary"; for my case. It's a zip file that I've renamed to
.txt in order to get around the attachment being blocked by
certain
"Relyea, Mike" <[EMAIL PROTECTED]> writes:
> I've zipped the results of EXPLAIN INSERT INTO "tblSummary" SELECT *
> FROM "qrySummary"; for my case. It's a zip file that I've renamed to
> .txt in order to get around the attachment being blocked by certain mail
> servers.
Egad, what a mess :-(. By
"Todd A. Cook" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Well, that's the problem right there :-(. Have you ANALYZEd this table?
> My production table and query are more complex. In the original, the
> query above was in a sub-select; the work-around was to create a temp
> table with the
I've zipped the results of EXPLAIN INSERT INTO "tblSummary" SELECT *
FROM "qrySummary"; for my case. It's a zip file that I've renamed to
.txt in order to get around the attachment being blocked by certain mail
servers.
PK yÖ4¨yï ý explain.txtí]]oÇÕ¾/[EMAIL
PROTECTED]( É`ç{ÖH
Tom Lane wrote:
"Todd A. Cook" <[EMAIL PROTECTED]> writes:
oom_test=> explain select val,count(*) from oom_tab group by val;
QUERY PLAN
-
HashAggregate (cost=1163446.13..1163448.63 rows=200
"Todd A. Cook" <[EMAIL PROTECTED]> writes:
"Todd A. Cook" <[EMAIL PROTECTED]> writes:
> QUERY PLAN
> -
> HashAggregate (cost=1163446.13..1163448.63 rows=200 width=4)
> -> Seq Scan on oo
"Todd A. Cook" <[EMAIL PROTECTED]> writes:
> oom_test=> explain select val,count(*) from oom_tab group by val;
> QUERY PLAN
> -
> HashAggregate (cost=1163446.13..1163448.63 rows=200 width=4)
>
Tom Lane wrote:
Misestimated hash aggregation, perhaps? What is the query and what does
EXPLAIN show for it? What have you got work_mem set to?
oom_test=> \d oom_tab
Table "public.oom_tab"
Column | Type | Modifiers
+-+---
val| integer |
oom_test=> explai
"Todd A. Cook" <[EMAIL PROTECTED]> writes:
> I am consistently running into out-of-memory issues in 8.1.4 running on
> RHEL3 and 8.0.5 on RHEL4. The logs show entries like this:
> AggContext: -2130714624 total in 271 blocks; 9688 free (269 chunks);
> -2130724312 used
> TupleHashTable: 893902872
ailto:[EMAIL PROTECTED]
Sent: Wednesday, June 21, 2006 11:01 PM
To: Relyea, Mike
Cc: pgsql-general@postgresql.org; Tom Lane
Subject: RE: [GENERAL] Out of memory error in 8.1.0 Win32
On Wed, 21 Jun 2006, Relyea, Mike wrote:
ExecutorState: 550339936 total in 123 blocks; 195003544 free (740135
c
So what's my next step? How do I track down what is causing this
problem?
-Original Message-
From: Qingqing Zhou [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 21, 2006 11:01 PM
To: Relyea, Mike
Cc: pgsql-general@postgresql.org; Tom Lane
Subject: RE: [GENERAL] Out of memory err
On Wed, 21 Jun 2006, Relyea, Mike wrote:
> ExecutorState: 550339936 total in 123 blocks; 195003544 free (740135
> chunks); 355336392 used
> HashBatchContext: 293593176 total in 44 blocks; 3107384 free (80
> chunks); 290485792 used
> TIDBitmap: 2088960 total in 8 blocks; 924720 free (27 chunks);
t: Re: [GENERAL] Out of memory error in 8.1.0 Win32
"Qingqing Zhou" <[EMAIL PROTECTED]> writes:
>> ExecutorState: 550339936 total in 123 blocks; 195005920 free (740144
>> chunks); 355334016 used
>> ...
>> HashBatchContext: 293593176 total in 44 blocks; 3107
"Qingqing Zhou" <[EMAIL PROTECTED]> writes:
>> ExecutorState: 550339936 total in 123 blocks; 195005920 free (740144
>> chunks); 355334016 used
>> ...
>> HashBatchContext: 293593176 total in 44 blocks; 3107384 free (80 chunks);
>> 290485792 used
> Er, looks like a huge hash-join but not sure if it
"Qingqing Zhou" <[EMAIL PROTECTED]> wrote
>
>
> ExecutorState: 550339936 total in 123 blocks; 195005920 free (740144
chunks); 355334016 used
> ...
> HashBatchContext: 293593176 total in 44 blocks; 3107384 free (80 chunks);
290485792 used
> TIDBitmap: 2088960 total in 8 blocks; 1012120 free (27 ch
""Relyea, Mike"" <[EMAIL PROTECTED]> wrote
> Is this what you're looking for?
No. I mean per-context memory usage output like this in your log file:
2006-06-08 16:33:09 LOG: autovacuum: processing database "ibox"
TopMemoryContext: 84400 total in 7 blocks; 12696 free (22 chunks); 71704
used
Oper
""Relyea, Mike"" <[EMAIL PROTECTED]> wrote
> I've just started receiving an out of memory error with my most complex
> query.
Can you post the memory usage log after the error the server reports?
Regards,
Qingqing
---(end of broadcast)---
TIP 6:
I've just started receiving an out of memory error with my most complex
query. It has been running fine for the past 9 months. It's a snapshot
materialized view that I update every night using the functions from
http://jonathangardner.net/PostgreSQL/materialized_views/matviews.html
The error I'm
21 matches
Mail list logo
