From: | strk(at)refractions(dot)net |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | postgis-devel(at)postgis(dot)refractions(dot)net |
Subject: | Re: GiST memory usage |
Date: | 2005-08-13 11:43:52 |
Message-ID: | 20050813114352.GA28208@keybit.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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, strk(at)refractions(dot)net 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;
From | Date | Subject | |
---|---|---|---|
Next Message | William ZHANG | 2005-08-13 12:47:30 | Re: CREATE USER and pg_user |
Previous Message | strk | 2005-08-13 11:12:30 | GiST memory usage |