| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | micah(at)colltech(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Memory bloating |
| Date: | 2000-10-03 19:01:57 |
| Message-ID: | 29619.970599717@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Micah Anderson <micah(at)colltech(dot)com> writes:
> NOTICE: --Relation webcast--
> NOTICE: Pages 2136: Changed 0, reaped 1781, Empty 0, New 0; Tup 1913:
> Vac 9561, Keep/VTL 0/0, Crash 0, UnUsed 1433, MinLen 726, MaxLen 6858;
> Re-using: Free/Avail. Space 14514420/14514420; EndEmpty/Avail. Pages
> 0/1781. CPU 0.14s/0.08u sec.
> NOTICE: Rel webcast: Pages: 2136 --> 356; Tuple(s) moved: 1913. CPU
> 0.29s/0.05u sec.
> VACUUM
Given the evident lack of any index on this table, it's not surprising
that your searches get slower and slower as more rows are added (or
updated). Think about adding appropriate indexes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2000-10-03 19:24:49 | Re: Memory bloating |
| Previous Message | Micah Anderson | 2000-10-03 19:01:43 | Re: Memory bloating |