| From: | strk <strk(at)keybit(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | postgis-devel(at)postgis(dot)refractions(dot)net |
| Subject: | index leaks ? |
| Date: | 2004-03-12 11:12:46 |
| Message-ID: | 20040312121246.A30735@freek.keybit.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
I'm watching a strange beahviour by postgres,
I wonder if it's a memory leak:
Creating an index and destroying it makes the
postgres process grow in size. This is what I do:
create table test (a int);
create index test_idx on test (a); drop index test_idx;
create index test_idx on test (a); drop index test_idx;
create index test_idx on test (a); drop index test_idx;
...
The size growth is reported by 'top' in the fields
SIZE, RSS and SHARE.
The database is a newly created one after first initdb
as of CVS 20040311.
Can it be a memory leak in postgres code ?
TIA
--strk;
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2004-03-12 11:39:03 | Re: [HACKERS] The Name Game: postgresql.net vs. pgfoundry.org |
| Previous Message | Alex J. Avriette | 2004-03-12 11:05:27 | Re: Timing of 'SELECT 1' |