Re: Why is materialized view creation a "security-restricted operation"?

From: Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Why is materialized view creation a "security-restricted operation"?
Date: 2026-10-04 19:27:34
Message-ID: 9da33cfb-661f-4088-9fad-04f6eb8fd21b@gelassene-pferde.biz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2026-10-04 20:24:41 Re: Why is materialized view creation a "security-restricted operation"?
Previous Message Ron Johnson 2026-10-02 15:18:38 Re: Why is materialized view creation a "security-restricted operation"?