Re: trouble with a join on OS X

From: Shane Ambler <pgsql(at)007Marketing(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kirk Wythers <kwythers(at)umn(dot)edu>, "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>, Gábriel Ákos <akos(dot)gabriel(at)i-logic(dot)hu>, pgsql-performance(at)postgresql(dot)org
Subject: Re: trouble with a join on OS X
Date: 2007-02-03 15:59:49
Message-ID: 45C4B175.1090707@007Marketing.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Tom Lane wrote:

> Since this is just a bog-standard Mini with 512M memory, it was pretty
> thoroughly on its knees by this point :-(. I'm not sure how to find out
> about allocated swap space in OS X, but my bet is that the above message
> should be understood as "totally out of virtual memory".

just so you can look into it for your own curiosity ;-) - Mac OS X uses
the startup disk for VM storage. You can find the files in - /var/vm

You will find the swapfiles there, the size of the swapfiles
progressively get larger - swapfile0 and 1 are 64M then 2 is 128M, 3 is
256M, 4 is 512M, 5 is 1G.... each is preallocated so it only gives you a
rough idea of how much vm is being used. You would run out when your
startup disk is full, though most apps probably hit the wall at 4G of vm
unless you have built a 64bit version.

The 4G (32bit) limit may be where you hit the out of memory errors (or
is postgres get around that with it's caching?).

--

Shane Ambler
pgSQL(at)007Marketing(dot)com

Get Sheeky @ http://Sheeky.Biz

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mark Stosberg 2007-02-03 19:00:26 optimizing a geo_distance() proximity query
Previous Message Tom Lane 2007-02-03 03:31:17 Re: trouble with a join on OS X