From: | Shane Ambler <pgsql(at)007Marketing(dot)com> |
---|---|
To: | Kirk Wythers <kwythers(at)umn(dot)edu> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-05 17:50:11 |
Message-ID: | 45C76E53.60104@007Marketing.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Kirk Wythers wrote:
>> The 4G (32bit) limit may be where you hit the out of memory errors (or
>> is postgres get around that with it's caching?).
>
> Any idea if postgres on OS X can truely access more that 4 gigs if the
> 64 bit version is built? I have tried building the 64 bit version of
> some other apps on OS X, and I have never been convinced that they
> behaved as true 64 bit.
>
I haven't tried myself
--
Shane Ambler
pgSQL(at)007Marketing(dot)com
Get Sheeky @ http://Sheeky.Biz
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Stosberg | 2007-02-05 19:47:25 | Re: optimizing a geo_distance() proximity query |
Previous Message | Kirk Wythers | 2007-02-05 04:29:52 | Re: trouble with a join on OS X |