Re: auto vacuum question

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Alan Stange <stange(at)rentec(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: auto vacuum question
Date: 2023-08-28 22:35:53
Message-ID: m0pm36aj7a.fsf@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:

> On 8/28/23 13:06, Alan Stange wrote:
>
>> All,
>> We recently changed the name of the superuser role in our database,

My take on this, is that the *postmaster* user is perhaps the one that
the OP cut privileges on, and thus the launcher is (now) spawning
workers with less than full SU perms.

Just a guess.

FWIW

>> and
>> then noticed some issues with the autovacuum processes.  We are running
>> 15.3, and had a login role, lets call it 'red', which had the superuser
>> attribute assigned to it.   This was the original owner/creator of all
>> the database objects, and the login role ended up getting used in some
>> ways for which the superuser attribute was no longer appropriate.
>> So we elected to make a new role, lets call it 'reddba', which had
>> tightly controlled entitlements, and which also had the super user
>> attribute added to it.  After a couple of weeks and a lot of testing, we
>> removed the superuser attribute from the original 'red' account.  All
>> was working as expected.
>> After a bit we noticed some warnings in the postgresql server log
>> file
>> of the form 'WARNING:    skipping "tablexxx"   --- only table of
>> database owner can vacuum it" where tablexxx is many of the table names
>> in our system.
>
> Are you sure that is coming from autovacuum?
>
> What are the log lines preceding the WARNING?
>
> What is the complete warning line?
>
>> We restored the superuser role to the original 'red' login role and
>> these messages went away.
>> We are not running any explicit vacuum's.    As far as I can tell,
>> these
>> warnings were comming from the autovacuum processes, and we did also
>> notice that some query stats became stale which I assume is related to
>> these same warnings.
>> So, I'm wondering how we can move the superuser role from role A to
>> B,
>> so that the autovacuum process will still work?   I googled around a
>> bit, but didn't come up with anything useful for this.
>> Thank you,
>> Alan
>>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stuart McGraw 2023-08-29 01:23:48 Restoring default privileges on objects
Previous Message Adrian Klaver 2023-08-28 20:48:59 Re: [INTERNET] Re: auto vacuum question