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

From David G. Johnston
Subject Re: Why is materialized view creation a "security-restricted operation"?
Date
Msg-id CAKFQuwZwX-L-c+=DS=_+kox_+p9AobWRWL7Fot48uAOt2t_X1Q@mail.gmail.com
Whole thread
In response to Re: Why is materialized view creation a "security-restricted operation"?  (Ron Johnson <ronljohnsonjr@gmail.com>)
Responses Re: Why is materialized view creation a "security-restricted operation"?
List pgsql-general
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."

David J.


pgsql-general by date:

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