On Sat, Jan 30, 2010 at 7:00 PM, Ray Stell 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 tab
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
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. Di
On Sat, Jan 30, 2010 at 10:28:37AM -0700, Scott Marlowe wrote:
> On Sat, Jan 30, 2010 at 7:59 AM, Ray Stell wrote:
> > Running 8.2.15 on RHEL4 the log reports this from autovacuum along with
> > other pg_ tables:
> Make yourself the owner of the database? (i.e. alter database ...)
autovacuum is
On Sat, Jan 30, 2010 at 7:59 AM, 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
>
> Any ideas how I can clean this up or how I got into this
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
Any ideas how I can clean this up or how I got into this hole?
Vacuum works as superuser.
Thanks.
--
Sent via pgs
