From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] vacuum process size |
Date: | 1999-08-18 14:02:42 |
Message-ID: | 24633.934984962@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> Just for a testing I made a huge table (>2GB and it has 10000000
> tuples). copy 10000000 tuples took 23 minutes. This is not so
> bad. Vacuum analyze took 11 minutes, not too bad. After this I created
> an index on int4 column. It took 9 minutes. Next I deleted 5000000
> tuples to see how long delete took. I found it was 6
> minutes. Good. Then I ran into a problem. After that I did vacuum
> analyze, and seemed it took forever! (actually took 47 minutes). The
> biggest problem was postgres's process size. It was 478MB! This is not
> acceptable for me. Any idea?
Yeah, I've complained about that before --- it seems that vacuum takes
a really unreasonable amount of time to remove dead tuples from an index.
It's been like that at least since 6.3.2, probably longer.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Herouth Maoz | 1999-08-18 14:08:11 | Re: [GENERAL] Re: [HACKERS] getting at the actual int4 value of an abstime |
Previous Message | Tom Lane | 1999-08-18 13:58:09 | Re: [HACKERS] Re: [CORE] Re: tomorrow |