Re: [HACKERS] Another nasty cache problem

From: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Another nasty cache problem
Date: 2000-02-03 18:47:07
Message-ID: 20000203184707.A2289@quartz.newn.cam.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 03, 2000 at 12:00:21PM -0500, Tom Lane wrote:
>
> The majority of Unix systems have a process size limit kernel parameter,
> which is normally set to less than the amount of available swap space
> (you don't want a single process running wild to chew up all your swap
> and make other stuff start failing for lack of swap...) Check your
> kernel parameters.

Probably to do with the shell limit:

memoryuse 125460 kbytes

> There's a separate question about *why* such a simple query is chewing
> up so much memory. What query plan does EXPLAIN show for your test
> query?

test=# explain select * from test,test2 where test.i!=test2.i;
NOTICE: QUERY PLAN:

Nested Loop (cost=64104.80 rows=1559400 width=56)
-> Seq Scan on test2 (cost=24.80 rows=600 width=28)
-> Seq Scan on test (cost=106.80 rows=2600 width=28)

EXPLAIN

> You said this was with current sources, right?

They're about 2 days old now. (Well, after your SI buffer overrun fixes)

Cheers,

Patrick

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2000-02-03 18:59:07 Re: [HACKERS] coming ColdFusion support for PostgreSQL
Previous Message Oliver Elphick 2000-02-03 18:41:28 Re: [HACKERS] Another nasty cache problem