Re: Memory bloating - Mailing list pgsql-general

From Tom Lane
Subject Re: Memory bloating
Date
Msg-id 29619.970599717@sss.pgh.pa.us
Whole thread Raw
In response to Memory bloating  (Micah Anderson <micah@colltech.com>)
List pgsql-general
Micah Anderson <micah@colltech.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

pgsql-general by date:

Previous
From: Micah Anderson
Date:
Subject: Re: Memory bloating
Next
From: "Ross J. Reedstrom"
Date:
Subject: Re: Memory bloating