From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>
To: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: Re: AW: Why is materialized view creation a "security-restricted operation"?
Date: Tue, 6 Oct 2026 14:38:00 -0700
Message-ID: <0f484041-00b6-454b-9def-e14a955d7c69@aklaver.com> (raw)
In-Reply-To: <886a7a1fb54a4abdbb89897a6854edd7@stmuk.bayern.de>
References: <77826d7580a9488ca28eb4bcfe94aa37@stmuk.bayern.de>
<61488cb9-5b84-449a-9886-e0d3b9671aa6@aklaver.com>
<CANzqJaCa34mEGBsTKZZQz7ZwDR3jd+Q0=s2_7ayw2hHFwTMXjw@mail.gmail.com>
<CAKFQuwZwX-L-c+=DS=_+kox_+p9AobWRWL7Fot48uAOt2t_X1Q@mail.gmail.com>
<CANzqJaBnOOer7V+AFk1uY86+uGfFj5EUCJLA0LvYyv9KCTksxg@mail.gmail.com>
<f6d2fca1-1ee4-4d97-8219-100dd91d8496@aklaver.com>
<886a7a1fb54a4abdbb89897a6854edd7@stmuk.bayern.de>
On 10/6/26 1:20 AM, Färber, Franz-Josef (StMUK) wrote:
> Are you sure the extension pgtt would work in my case?
>
> https://github.com/darold/pgtt#how-the-extension-really-works says:
>
> "the first access to the table using a SELECT, UPDATE or DELETE statement will produce the creation of a temporary table"
>
> Well, my original point was: Creation of a temporary table is prohibited due to "security-restricted operation".
I tried your MATERIALIZED VIEW with pgtt and ran into the temporary
table issue. I tried also against the 'template' table behind the
temporary tables and got a little further but the behavior was unstable.
I suspect a bug that allowed me to get that far.
Questions:
1) Why the MATERIALIZED VIEW?
2) Can you provide an overview in pseudo code, including the part in the
function, of the process you are trying create?
>
>
> Regards,
> Franz-Josef Färber
>
>
> -----Ursprüngliche Nachricht-----
> Von: Adrian Klaver <adrian.klaver@aklaver.com>
> Gesendet: Freitag, 2. Oktober 2026 16:55
> An: Ron Johnson <ronljohnsonjr@gmail.com>; pgsql-general <pgsql-general@postgresql.org>
> Betreff: Re: Why is materialized view creation a "security-restricted operation"?
>
> 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!
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: adrian.klaver@aklaver.com, Franz-Josef.Faerber@stmuk.bayern.de
Subject: Re: AW: Why is materialized view creation a "security-restricted operation"?
In-Reply-To: <0f484041-00b6-454b-9def-e14a955d7c69@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox