From: Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>
To: Christophe Pettus <xof@thebuild.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: AW: Why is materialized view creation a "security-restricted operation"?
Date: Tue, 13 Oct 2026 06:23:22 +0000
Message-ID: <9b969e375e504257b41fda27f140c165@stmuk.bayern.de> (raw)
In-Reply-To: <81F7B946-997E-496E-BABC-514F9F0E9FFB@thebuild.com>
References: <77826d7580a9488ca28eb4bcfe94aa37@stmuk.bayern.de>
<2e9d29c1513afb47d652387ea5299076ef24adce.camel@cybertec.at>
<f69b47dbbe374bac8088887c21193f26@stmuk.bayern.de>
<9f30126c-9e72-4ced-83e2-3f8e5da183d3@aklaver.com>
<569054683acf4de7a3f2de80391b4e71@stmuk.bayern.de>
<81F7B946-997E-496E-BABC-514F9F0E9FFB@thebuild.com>
Yes, Thank you. I mentioned that here, with its disadvantage: https://www.postgresql.org/message-id/f69b47dbbe374bac8088887c21193f26%40stmuk.bayern.de :
> What I COULD do is replace COPY x ... FROM PROGRAM with a file_fdw FOREIGN TABLE, but this way it isn't parametrizable. I would have to create as many foreign tables as I have passwords / environment variables, I think.
Regards,
Franz-Josef Färber
-----Ursprüngliche Nachricht-----
Von: Christophe Pettus <xof@thebuild.com>
Gesendet: Dienstag, 13. Oktober 2026 08:19
An: Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>; pgsql-general@postgresql.org
Betreff: Re: Why is materialized view creation a "security-restricted operation"?
Hi,
> On Oct 12, 2026, at 23:12, Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de> wrote:
>
> Thanks for the suggestion.
> But what exactly is the suggestion?
>
> At least I understand DuckDB can directly read without having to craete a temp table:
> * SELECT * FROM 'test.csv.gz';
> * SELECT * FROM read_csv('test.csv', header = false);
>
> ... which is what Postgres is missing.
PostgreSQL implements this using foreign data wrappers.
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, xof@thebuild.com, adrian.klaver@aklaver.com
Subject: Re: AW: Why is materialized view creation a "security-restricted operation"?
In-Reply-To: <9b969e375e504257b41fda27f140c165@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