"Ross J. Reedstrom" <[EMAIL PROTECTED]> writes:
> My guess is it's an interaction of the optimizer with the plan for this
> query, which might have many, nearly identical cost plans, since 8 of
> the 9 tables are actually the same table.
Yes, I suspect the same. A large fraction of the possible
Cc: PostgreSQL Admin
> Subject: Re: [ADMIN] High memory usage
>
>
> "Rainer Mager" <[EMAIL PROTECTED]> 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 doe
"Rainer Mager" <[EMAIL PROTECTED]> 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 o
Thanks for the reply.
I can try to explain the query but it is being generated semi-automatically
so it is not hard coded for a particular purpose. Before going into the
explanation, though, I have a litte bit of new information. First, it is
ONLY the join condition that matters, the other param
Ranier -
Can you explain in words what this query is supposed to be doing?
I'm guessing, from the DISTINCT, and the use of multiple occurances of
the same table, that the result you want can be gotten at in some other
way, that lets the backend be smarter about how it does it. Since it _is_
rele
Admin
> Subject: RE: [ADMIN] High memory usage
>
>
> Hi,
>
> Here is a query that demonstrates the problem. Running this
> takes about 60MB until it is done at which time it is freed (I
> was wrong when I said otherwise earlier). Interestingly, the same
> amount of me
o:[EMAIL PROTECTED]]On Behalf Of Tom Lane
> Sent: Thursday, June 14, 2001 10:03 AM
> To: Rainer Mager
> Cc: PostgreSQL Admin
> Subject: Re: [ADMIN] High memory usage
>
>
> There's not a lot more we can say about it until you can identify the
> query that sucks up all the
done
something wrong. If this diff doesn't apply please tell me.
--Rainer
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rainer Mager
> Sent: Wednesday, June 20, 2001 9:08 AM
> To: Tom Lane
> Cc: PostgreSQL Admin
> Subject
as already done this I would be
grateful.
--Rainer
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lane
> Sent: Thursday, June 14, 2001 10:03 AM
> To: Rainer Mager
> Cc: PostgreSQL Admin
> Subject: Re: [ADMIN] High memory u
"Rainer Mager" <[EMAIL PROTECTED]> writes:
> First of all we see some of the PG processes use as much as 80 MB
> (according to top and ps). This seems to be allocated during a query
> (SELECT). Unfortunately, we haven't been able to discover exactly what query
> is doing this.
If you can ca
Hi all,
We're seeing one usage of a database use significant more memory than
we're used to and I'm hoping for some hints at what Postgres allocates
memory for. BTW, we're running PG 7.1 on Linux.
First of all we see some of the PG processes use as much as 80 MB
(according to top
11 matches
Mail list logo
