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

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Färber, Franz-Josef (StMUK) <Franz-Josef(dot)Faerber(at)stmuk(dot)bayern(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: AW: AW: Why is materialized view creation a "security-restricted operation"?
Date: 2026-10-13 15:52:14
Message-ID: affe49ac-9ee6-4b21-991e-a9a35bebfd68@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/12/26 11:12 PM, Färber, Franz-Josef (StMUK) wrote:
> Thanks for the suggestion.
> But what exactly is the suggestion?

That you also read the links included, where it shows that DuckDb is
available from a multitude of languages and can connect to a Postgres
database to share information. Think it of as in-memory database to do
the scratch work that you then pass into Postgres. It is definitely a
round about way of tackling the problem.

>
> 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.
>
>
> Regards,
> Franz-Josef Färber
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2026-10-13 16:23:19 Re: AW: Why is materialized view creation a "security-restricted operation"?
Previous Message Rob Sargent 2026-10-13 15:36:47 Re: Why is materialized view creation a "security-restricted operation"?