Ok, I replaced names of tables and columns and here is the query
explain (analyze, verbose, settings, format text) create table
dm.v_Table6_T_1 with (fillfactor = 100, parallel_workers = 20,
autovacuum_enabled = false, toast.autovacuum_enabled = false) as select
VHS.df_v_Table2_k
Dear community,
We see significant difference in explain analyze Actual time in the first line
of execution plan and Execution time in the last line of execution plan. What
can be the reason?
For example, first line of execution plan:
Gather (cost=1038.49..257627100.42 rows=794326 width=10
was introduced in Posgres 16, does it mean, that Posgres 15.8 should
have old behaviour?
We dont use COPY in our queries.
-Original Message-
From: Thomas Munro
Sent: Wednesday, September 11, 2024 11:37 PM
To: Alvaro Herrera
Cc: Pecsök Ján ; pgsql-general@lists.postgresql.org;
Andres
Ján
Cc: Thomas Munro ; pgsql-general@lists.postgresql.org;
Andres Freund
Subject: Re: Error:could not extend file " with FileFallocate(): No space left
on device
On 2024-Sep-11, Pecsök Ján wrote:
> In our case:
> Kernel: Linux version 4.18.0-513.18.1.el8_9.ppc64le
> (mockb
, September 11, 2024 12:45 PM
To: Alvaro Herrera
Cc: Pecsök Ján ; pgsql-general@lists.postgresql.org;
Andres Freund
Subject: Re: Error:could not extend file " with FileFallocate(): No space left
on device
On Wed, Sep 11, 2024 at 9:56 PM Alvaro Herrera wrote:
> On 2024-Sep-10, Pecsök J
Dear community,
After upgrade of Posgres from version 13.5 to 16.2 we experience following
error:
could not extend file "pg_tblspc/16401/PG_16_202307071/17820/3968302971" with
FileFallocate(): No space left on device
We cannot easily replicate problem. It happens at randomly every 1-2 weeks of
