I set nested_loop = off, which is why I have the high cost.
@ is a postgis operator between 2 geomotries (both polygons). It's the @
operator which is expensive. Is there a way to force a cheaper way of
doing that join?
-> Nested Loop (cost=11905.94..11906.08 rows=1
width=68) (
Hi,
We have been running PostgreSQL 7.3.4 on 64 bit MAC OS X G5 dual
processors with 8GB of RAM for a while.
Lately, we realized that consistently only about 4GB of RAM is used
even when CPUs have maxed out
for postgtres processes and pageouts starts to happen. Here is a
portion of the output f
On Mon, Sep 20, 2004 at 07:57:34PM +1200, Guy Thornley wrote:
[snip]
>
> Incidentally, postgres heap files suffer really, really bad fragmentation,
> which affects sequential scan operations (VACUUM, ANALYZE, REINDEX ...)
> quite drastically. We have in-house patches that somewhat alleiviate this,
