| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Ray Stell <stellr(at)cns(dot)vt(dot)edu> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: VACUUM WARNING: skipping "pg_statistic" --- only table or database owner can vacuum it |
| Date: | 2010-01-31 02:18:52 |
| Message-ID: | dcc563d11001301818q750b97a7wa98f883c002dc4c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sat, Jan 30, 2010 at 7:00 PM, Ray Stell <stellr(at)cns(dot)vt(dot)edu> wrote:
> On Sat, Jan 30, 2010 at 10:35:27PM -0300, Alvaro Herrera wrote:
>> Ray Stell wrote:
>> > Running 8.2.15 on RHEL4 the log reports this from autovacuum along with
>> > other pg_ tables:
>> >
>> > VACUUM WARNING: skipping "pg_database" --- only table or database owner can vacuum it
>>
>> Huh, that's pretty weird ... autovacuum is supposed to connect as
>> superuser internally. Did you do something funny to the system role
>> (typically called "postgres")?
>
>
> agreed. If I did, I don't know what it was. I suppose I'm reduced
> to creating a new cluster and restoring the apps into it, unless
> somebody can suggest an audit method that would uncover the injury.
Whoa, don't burn down the village just yet.
What does \du postgres say?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ray Stell | 2010-01-31 18:44:10 | Re: VACUUM WARNING: skipping "pg_statistic" --- only table or database owner can vacuum it |
| Previous Message | Ray Stell | 2010-01-31 02:00:01 | Re: VACUUM WARNING: skipping "pg_statistic" --- only table or database owner can vacuum it |