| From: | Mark Lubratt <mark(dot)lubratt(at)indeq(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: postgres eating CPU on HP9000 |
| Date: | 2004-03-29 17:23:49 |
| Message-ID: | D7D66D46-81A5-11D8-856C-000A9579AF50@indeq.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mar 29, 2004, at 9:36 AM, Tom Lane wrote:
> "Marcus Andree S. Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br> writes:
>>> Also do you run VACUUM ANALYZE as a superuser, or as a regular user?
>
>> As a regular user (database owner). Is thery any difference when
>> vacuuming
>> as a super user?
>
> That's your problem. A regular user won't have permissions to vacuum
> any tables but his own ... in particular, not the system tables.
>
> regards, tom lane
If I vacuum as the superuser, are the system tables automatically
vacuumed? Or, does using -a from the vacuumdb command accomplish this?
Or, is there something else I have to specify on the vacuumdb command
line?
Thanks!
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Rawnsley | 2004-03-29 17:25:35 | Re: column size too large, is this a bug? |
| Previous Message | Jaime Casanova | 2004-03-29 17:05:00 | Re: column size too large, is this a bug? |