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

From: Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>
To: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Why is materialized view creation a "security-restricted operation"?
Date: 2026-10-07 05:51:27
Message-ID: 6271bc72-7a03-48cd-b900-adf6bbf4a1ec@gelassene-pferde.biz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

06.10.2026 23:50:14 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:

>
> Does that issue not also exist with persistent tables, where the data you are looking in the debugging stage maybe not be what was present at the error stage?
>
To a lesser extent, depending on the design of the process. At least one has got some chance.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kartik, Vaibhav 2026-10-07 07:44:52 Regarding the General Availability of Postgres19 and its features
Previous Message shihao zhong 2026-10-07 01:38:43 Re: Capture a changelog for the current transaction