| From: | Shelby Cain <alyandon(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org>, pgsql-hackers-win32(at)postgresql(dot)org |
| Subject: | Re: Postgresql 8.0 beta 1 - strange cpu usage statistics and slow vacuuming |
| Date: | 2004-08-24 18:00:00 |
| Message-ID: | 20040824180000.2456.qmail@web41602.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers-win32 |
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> IIRC, vacuum fsyncs once per table (possibly more
> depending on whether
> you add FULL, ANALYZE, etc). Not clear what case
> you are considering
> exactly.
>
Vacuum and Vacuum full. The script I attached to a
previous post to demonstrate the behavior (at least on
this workstation) creates and populates a single table
via a stored procedure, updates approximately half the
rows and then executes a vacuum followed by a vacuum
full.
The insert and update commands execute far faster
(showing 5-10 megs of disk transfer per second on
average) than both the vacuum and vacuum full (showing
512k to 1meg of transfer per second).
Regards,
Shelby Cain
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-08-24 18:07:37 | Re: Invalid input for integer on VIEW |
| Previous Message | mike | 2004-08-24 17:42:52 | Re: Invalid input for integer on VIEW |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2004-08-24 18:16:33 | Re: REPOST: InitDB Failure on install |
| Previous Message | Magnus Hagander | 2004-08-24 17:43:54 | Re: REPOST: InitDB Failure on install |