Re: Why is materialized view creation a "security-restricted operation"? - Mailing list pgsql-general

From Thiemo Kellner
Subject Re: Why is materialized view creation a "security-restricted operation"?
Date
Msg-id 9da33cfb-661f-4088-9fad-04f6eb8fd21b@gelassene-pferde.biz
Whole thread
In response to Re: Why is materialized view creation a "security-restricted operation"?  (Färber, Franz-Josef (StMUK)<Franz-Josef.Faerber@stmuk.bayern.de>)
Responses Re: Why is materialized view creation a "security-restricted operation"?
List pgsql-general
Hi

Giving my two dimes. I apologise if some else has given it already. And it is quite an operations point of view and mostly based on Oracle. To the best of my knowledge, it applies to Postgres even more.

The data of DB temp tables are not visible outside of the session that has put it in. In the case of trying to find the problem of code of functions storing intermediary results, they are just not visible for the investigator such that one has to do all the steps manually to detect the point where things go wrong. In my opinion a real pita.

Cheers

Thiemo

pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Why is materialized view creation a "security-restricted operation"?
Next
From: Adrian Klaver
Date:
Subject: Re: Why is materialized view creation a "security-restricted operation"?