From: Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>
To: Rob Sargent <robjsargent@gmail.com>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: AW: Why is materialized view creation a "security-restricted operation"?
Date: Wed, 14 Oct 2026 17:38:03 +0000
Message-ID: <42c29de0b9ed4fa89159a3ed8831ff54@stmuk.bayern.de> (raw)
In-Reply-To: <9B7D623E-1DEF-46DC-92B3-FF9452624F5C@gmail.com>
References: <3b50a3393fd84d56b40cfddd67c98dbc@stmuk.bayern.de>
<9B7D623E-1DEF-46DC-92B3-FF9452624F5C@gmail.com>
Yes, I would have to predefine the columns.
In my case it's just one column, one row, which i wanted to load from an external file.
Regards,
Franz-Josef Färber
-----Ursprüngliche Nachricht-----
Von: Rob Sargent <robjsargent@gmail.com>
Gesendet: Dienstag, 13. Oktober 2026 17:37
An: Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>; Adrian Klaver <adrian.klaver@aklaver.com>; pgsql-general@postgresql.org; Haupt, Matthias (StMUK) <Matthias.Haupt@stmuk.bayern.de>
Betreff: Re: Why is materialized view creation a "security-restricted operation"?
> On Oct 13, 2026, at 08:17, Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de> wrote:
>
>
>>
>> Well, you want to use a materialized view for something that it cannot be used for, for security reasons. We tried to explain that in this thread.
> Yes, you can see it this way: One way would be: Using Temp Tables. This way is blocked due to security reasons. Discussion finished.
>
> Another point of view is:
> 0) The security problem is not inherent for what I was trying to archieve; but due to lack of expressiveness one is forced into this dead end.
> 1) Either: Postgres' COPY stmt lacks the ability to omit the physical table, something like SELECT * FROM COPY FROM ...
> 2) or: Postgres lacks table variables.
>
I am not clear on your workflow so these questions come to mind:
What do you do with the undefined “*” (if it were allowed)?
Would you not have to predefine the columns of the table variable?
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: Franz-Josef.Faerber@stmuk.bayern.de, robjsargent@gmail.com
Subject: Re: AW: Why is materialized view creation a "security-restricted operation"?
In-Reply-To: <42c29de0b9ed4fa89159a3ed8831ff54@stmuk.bayern.de>
* 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