From: | Tobias Lott <tobias(dot)lott(at)devoteam(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: permission denied for pg_temp_XX when vacuuming |
Date: | 2021-03-03 16:02:21 |
Message-ID: | CANCOamzGsTavN-JyMp85yAJRFB2bXberotvWFjn_SkFHg6jg_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes that's strange. A lot of pg_XX tables are skipped, but some of these
pg_temp schemas cause errors.
Could it be connected to a migration of the database (from an instance
running PostgreSQL 9.6 to an instance running PostgreSQL 12) done a few
weeks ago?
Regards,
Tobias
On Wed, 3 Mar 2021 at 16:15, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> > On Wed, 2021-03-03 at 09:58 +0100, Tobias Lott wrote:
> >> I have a database in a PostgreSQL 12 instance.
> >> When running vacuumdb -z on the database with the user set as owner of
> the DB, I sometimes, not always, get errors such as:
> >> error: vacuuming of table "pg_temp_93.vacuum_l" in database "10050"
> failed: ERROR: permission denied for schema pg_temp_93
> >> The specific number of the pg_temp schema (pg_temp_XX) is always
> changing. What could be the reason for this error?
>
> > Those are schemas for temporary tables, which you cannot VACUUM outside
> the
> > session that created them, so you can safely ignore these errors.
>
> Indeed, but I'm wondering why vacuumdb isn't skipping them
> automatically. Something fishy seems to be happening there.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2021-03-03 16:08:17 | Re: Duplicate key error |
Previous Message | Adrian Klaver | 2021-03-03 15:42:20 | Re: Duplicate key error |