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

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(at)thebuild(dot)com>
Gesendet: Dienstag, 13. Oktober 2026 08:19
An: Färber, Franz-Josef (StMUK) <Franz-Josef(dot)Faerber(at)stmuk(dot)bayern(dot)de>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>; pgsql-general(at)postgresql(dot)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(dot)Faerber(at)stmuk(dot)bayern(dot)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.