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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why is materialized view creation a "security-restricted operation"?
Date: 2026-10-02 00:34:42
Message-ID: CAKFQuwZwX-L-c+=DS=_+kox_+p9AobWRWL7Fot48uAOt2t_X1Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

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."

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2026-10-02 10:19:20 Re: Why is materialized view creation a "security-restricted operation"?
Previous Message Ron Johnson 2026-10-02 00:03:17 Re: SQL_NEED__DATA