| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mindaugas Riauba <mind(at)bi(dot)lt>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Degrading performance |
| Date: | 2003-06-02 17:42:48 |
| Message-ID: | Pine.LNX.4.33.0306021142180.12320-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 2 Jun 2003, Tom Lane wrote:
> "scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
> > On Mon, 2 Jun 2003, Tom Lane wrote:
> >>> INFO: Rel ifdata: Pages: 4887 --> 17; Tuple(s) moved: 776.
> >>> CPU 0.30s/0.35u sec elapsed 1.65 sec.
> >>
> >> That says you waited way too long to vacuum --- over two hundred update
> >> cycles, evidently.
>
> > Don't forget to crank up your fsm settings in $PGDATA/postgresql.conf as
> > well.
>
> The table's not very big though. As long as he keeps after it with
> sufficiently-frequent vacuuming, it won't need much FSM space.
Yeah, but I got the feeling he was updating like 40 rows a second or
something. Sufficiently frequent for him may well be constant. :-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yusuf | 2003-06-05 15:35:22 | Enabling and disabling run time configuration parameters. |
| Previous Message | Tom Lane | 2003-06-02 17:25:22 | Re: Degrading performance |