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

From Ron Johnson
Subject Re: Why is materialized view creation a "security-restricted operation"?
Date
Msg-id CANzqJaBnOOer7V+AFk1uY86+uGfFj5EUCJLA0LvYyv9KCTksxg@mail.gmail.com
Whole thread
In response to Re: Why is materialized view creation a "security-restricted operation"?  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Why is materialized view creation a "security-restricted operation"?
List pgsql-general
On Thu, Oct 1, 2026 at 8:35 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Thu, Oct 1, 2026 at 4:56 PM Ron Johnson <ronljohnsonjr@gmail.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!

pgsql-general by date:

Previous
From: "David G. Johnston"
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"?