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

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why is materialized view creation a "security-restricted operation"?
Date: 2026-10-02 10:19:20
Message-ID: CANzqJaBnOOer7V+AFk1uY86+uGfFj5EUCJLA0LvYyv9KCTksxg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 1, 2026 at 8:35 PM David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Thu, Oct 1, 2026 at 4:56 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
> wrote:
>
>> A GLOBAL TEMP table (where the DBA runs the CREATE GLOBAL TEMP TABLE
>> once (so that CREATE TEMP TABLE some_table everywhere that my_func()
>> is called) would also solve OP's problem.
>>
>
> Per the create table docs:
>
> "Optionally, GLOBAL or LOCAL can be written before TEMPORARY or TEMP.
> This presently makes no difference in PostgreSQL and is deprecated; see
> Compatibility below."
>

And I'm praying for "since future versions of PostgreSQL might adopt a more
standard-compliant interpretation of their meaning" in the
Compatibility section you referenced.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2026-10-02 14:54:31 Re: Why is materialized view creation a "security-restricted operation"?
Previous Message David G. Johnston 2026-10-02 00:34:42 Re: Why is materialized view creation a "security-restricted operation"?