Missing info for the report:
win32
postgresql 8.0.3
maintenance_work_mem 512
btree index on oid works fine
--strk;
On Sat, Aug 13, 2005 at 01:12:30PM +0200, [EMAIL PROTECTED] wrote:
> Hi all.
> I've been reported memory limit hits
> during a postgis index construction
> (GiST index).
>
> The indexed tuples are about 425 millions.
> The index key is a box2d object (4*sizeof(float)).
>
> The machine has 4 Gb of RAM, and operations are
> peaked at ~2.4 Gb of usage.
>
> Is there a way to detect where is memory hold ?
>
> Is there an index-specific memory context for use
> to early release memory blocks allocated during
> operations (didn't see any use of memory contexts
> in the contrib/rtree_gist) ?
>
> TIA
>
> --strk;
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
