| From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
|---|---|
| To: | "Phillip Berry" <pberry(at)stellaconcepts(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Maximum reasonable free space map |
| Date: | 2008-12-17 02:52:44 |
| Message-ID: | 2f4958ff0812161852r2efb3dd6n8119b5c237769e23@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Dec 17, 2008 at 2:29 AM, Phillip Berry
<pberry(at)stellaconcepts(dot)com> wrote:
>
> The data in nearly every table is constantly changing due to a high volume of new data constantly
> coming in, processing on the existing data and heavy reporting being done all at once all day and
> night.
>
> So I guess my question is, is there a point where you start to see diminishing returns or even
> negative returns by setting the fsm too high?
I personally didn't experience anything like that.
If the data is updated, but not deleted mostly - you should do
something to utilize HOT (if using 8.3).
Otherwise, you want FSM to be big enough - so that more and more
deleted records could get reused without need for so often vacuum.
--
GJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivanmara | 2008-12-17 03:55:43 | Rows count in the cursor ? |
| Previous Message | Phillip Berry | 2008-12-17 02:29:33 | Re: Maximum reasonable free space map |