Re: GiST memory usage
| От | strk@refractions.net |
|---|---|
| Тема | Re: GiST memory usage |
| Дата | |
| Msg-id | 20050813114352.GA28208@keybit.net обсуждение исходный текст |
| Ответ на | GiST memory usage (strk@refractions.net) |
| Список | pgsql-hackers |
Missing info for the report:win32postgresql 8.0.3maintenance_work_mem 512btree index on oid works fine --strk; On Sat, Aug 13, 2005 at 01:12:30PM +0200, strk@refractions.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;
В списке pgsql-hackers по дате отправления: