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

From Adrian Klaver
Subject Re: Why is materialized view creation a "security-restricted operation"?
Date
Msg-id f6d2fca1-1ee4-4d97-8219-100dd91d8496@aklaver.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 10/2/26 3:19 AM, Ron Johnson wrote:
> On Thu, Oct 1, 2026 at 8:35 PM David G. Johnston 
> <david.g.johnston@gmail.com <mailto:david.g.johnston@gmail.com>> wrote:
> 
>     On Thu, Oct 1, 2026 at 4:56 PM Ron Johnson <ronljohnsonjr@gmail.com
>     <mailto: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 PostgreSQLmight adopt a 
> more standard-compliant interpretation of their meaning" in the 
> Compatibility section you referenced.

As an extension there is:

https://github.com/darold/pgtt

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


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

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