| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Tobias Lott <tobias(dot)lott(at)devoteam(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: permission denied for pg_temp_XX when vacuuming |
| Date: | 2021-03-03 15:15:46 |
| Message-ID: | 1180816.1614784546@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 15:23:35 | Duplicate key error |
| Previous Message | Magnus Hagander | 2021-03-03 11:50:28 | Re: problems with my community account on www.postgresql.org |