From: | Tycho Fruru <tycho(at)fruru(dot)com> |
---|---|
To: | Jeff Boes <jboes(at)nexcerpt(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: VACUUM on multi-CPU systems? |
Date: | 2002-09-06 14:19:59 |
Message-ID: | 1031322000.1117.25.camel@kungfoo.conostix.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, 2002-09-06 at 16:14, Jeff Boes wrote:
> On Mon, 26 Aug 2002 12:04:23 -0400, Jeff Boes wrote:
>
> > Does anyone have any thoughts on whether my database vacuum/full/analyze
> > might go faster on our 2-CPU system if I generated the VACUUM commands
> > into a script, e.g.,
> >
> > psql -a <<EOF
> > \t
> > \o /tmp/db_maint.$$
> > select distinct on (relname) 'VACUUM FULL ANALYZE "' || relname || '";'
> > from pg_class
> > where relkind='r'
> > \g
> > \o
> > EOF
> >
> > (generates a script that looks like
> >
> > VACUUM FULL ANALYZE table1;
> > VACUUM FULL ANALYZE table2;
> >
> > etc.)
> >
> > and then started two psql sessions each processing half of the file?
>
> I didn't see any response to this, so I'll try just one more time and
> then shut up ...
I think that vacuum will be more rapidly disk-bound then CPU-bound.
So if you've got different spindles for your tables, go ahead and
perform multiple vacuum full's at the same time (even on a uniprocessor
machine)
The proof of the pudding is of course what you all know (and like !)
Tycho
--
Tycho Fruru tycho(at)fruru(dot)com
"Prediction is extremely difficult. Especially about the future."
- Niels Bohr
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-06 14:38:30 | Re: Remote monitoring |
Previous Message | Jeff Boes | 2002-09-06 14:14:14 | Re: VACUUM on multi-CPU systems? |