From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Nature Conservation Geovista Space <conservation(dot)by(dot)geovista(dot)space(at)gmail(dot)com>, pgsql-novice(at)lists(dot)postgresql(dot)org |
Subject: | Re: Even if I have a lot of free space PgSQL returns "ERROR: could not extend file - No space left on device" |
Date: | 2023-09-08 17:51:15 |
Message-ID: | 5520a74bc59f5aed4b29772b04c28d58566013a2.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Fri, 2023-09-08 at 12:22 +0100, Nature Conservation Geovista Space wrote:
> After hours running a query to Subdivide, I get this Postgres error
> >
> > 2023-09-08 02:11:23.745 BST [328594] postgres(at)database ERROR: could not extend file "base/16388/7985375.1020": No space left on device
> > 2023-09-08 02:11:23.745 BST [328594] postgres(at)database HINT: Check free disk space.
> >
> > 2023-09-08 02:11:23.745 BST [328594] postgres(at)database STATEMENT: CREATE TABLE _gaul_administrative_subdivided100 AS (
> > SELECT *, st_subdivide(geom,100) AS geom_subdivided100
> > FROM gaul_administrative
> > );
>
> It seems that it is not a problem of space. [df shows there is space everywhere]
"After running a query for hours" makes it appear like you run out of disk space with
temporary files. These only exist during the lifetime of the query, so they are gone again after
the statement has failed.
Set "temp_file_limit" to avoid that kind of problem.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | bruno da silva | 2023-09-08 20:01:03 | Re: Even if I have a lot of free space PgSQL returns "ERROR: could not extend file - No space left on device" |
Previous Message | Nature Conservation Geovista Space | 2023-09-08 11:22:58 | Even if I have a lot of free space PgSQL returns "ERROR: could not extend file - No space left on device" |