From: | "Rainer Mager" <rmager(at)vgkk(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "PostgreSQL Admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | RE: High memory usage |
Date: | 2001-06-21 02:17:13 |
Message-ID: | NEBBJBCAFMMNIHGDLFKGGEIIEFAA.rmager@vgkk.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-jdbc pgsql-patches |
This looks very promising. I'll have to look over it and try a few things
out but I think it puts me on the right track.
Thanks!
--Rainer
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Thursday, June 21, 2001 10:56 AM
> To: Rainer Mager
> Cc: PostgreSQL Admin
> Subject: Re: [ADMIN] High memory usage
>
>
> "Rainer Mager" <rmager(at)vgkk(dot)com> writes:
> > First, this type of query seems to use exponential amounts of memory.
>
> Hmm. What does EXPLAIN show as the plan for the query? How long does
> it take to do the EXPLAIN? If the EXPLAIN alone takes a lot of time/
> space, then you need to reduce the size of the planner's search space
> with an explicit JOIN --- see
> http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/explic
> it-joins.html
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-21 02:52:28 | Re: High memory usage |
Previous Message | Bruce Momjian | 2001-06-21 02:08:04 | Re: High memory usage [PATCH] |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-21 02:52:28 | Re: High memory usage |
Previous Message | Bruce Momjian | 2001-06-21 02:08:04 | Re: High memory usage [PATCH] |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-06-21 02:52:28 | Re: High memory usage |
Previous Message | Bruce Momjian | 2001-06-21 02:08:04 | Re: High memory usage [PATCH] |