Re: No enough privileges for autovacuum worker

Поиск
Список
Период
Сортировка
От Adrian Klaver
Тема Re: No enough privileges for autovacuum worker
Дата
Msg-id 9c987b8d-6690-211a-2795-d33bd0de36ef@aklaver.com
обсуждение исходный текст
Ответ на Re: No enough privileges for autovacuum worker  (Андрей Сычёв <andrey.sychev@cifrasoft.com>)
Список pgsql-general
On 3/25/21 1:25 AM, Андрей Сычёв wrote:
> Because   in  trigger  where  table  fpbackup.fp_vpn_data_2021w12  has
> been created there are several DDL commands:
> 
> EXECUTE 'CREATE TABLE "' || fp_schema_name || '"."' || fp_table_name || '" (LIKE '|| fp_parent_table_name || '
INCLUDINGDEFAULTS INCLUDING CONSTRAINTS INCLUDING INDEXES) WITHOUT OIDS TABLESPACE ' || fp_tablespace;
 
> 
> EXECUTE 'ALTER TABLE "' || fp_schema_name || '"."' || fp_table_name || '" OWNER TO fpbkwriter';
> 
> The  trigger was called by user "worker" that already had permission on
> USAGE  of schema dict, so table creation was successful. But after that
> the ownership of the table was moving to "fpbkwriter" that had no permission on
> USAGE of schema dict, thus the error occured.
> 
> In reality, there was no user "fpbkwriter" at the beginning. Only user
> "worker"  was  created. And when the user "fpbkwriter" was created, he  was
> not granted by enough privileges mistakenly.
> 

Alright that I understand. Still after the ALTER TABLE ... OWNER TO 
fpbkwriter, the index was running as fpbkwriter yet there where no 
errors? Did that mean the table was never queried or the index never used?


-- 
Adrian Klaver
adrian.klaver@aklaver.com



В списке pgsql-general по дате отправления:

Предыдущее
От: Андрей Сычёв
Дата:
Сообщение: Re: No enough privileges for autovacuum worker
Следующее
От: Paul van der Linden
Дата:
Сообщение: Re: Slow index creation