Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qefdc-007QSz-38 for pgsql-novice@arkaria.postgresql.org; Fri, 08 Sep 2023 17:51:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qefda-00C4SD-O3 for pgsql-novice@arkaria.postgresql.org; Fri, 08 Sep 2023 17:51:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qefda-00C4Rx-Eb for pgsql-novice@lists.postgresql.org; Fri, 08 Sep 2023 17:51:22 +0000 Received: from mail-ed1-x52a.google.com ([2a00:1450:4864:20::52a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qefdX-003TVA-13 for pgsql-novice@lists.postgresql.org; Fri, 08 Sep 2023 17:51:20 +0000 Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-52a5c0d949eso3054241a12.0 for ; Fri, 08 Sep 2023 10:51:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1694195476; x=1694800276; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=BRb6+fsKG46EDKfnC4YLlAaWiUIkKEFKYbSuoOYomDM=; b=bWPiPkbuR8P6fz5yVMSotExYGKdCLOUfZeAI835AKLR9uTzWT0BEKFh5o3w2Z/ePSB el4d7GtCuPyR/ZHyuCK8ODU7YKPQCCchnfIf88uO4ZMr9PI8LI7adXH6lTMRuEc7L5WX zkAVcV6Fwm6VdswQfs71Q0Mg9MVu62Qgvl8SgX4SRzczt86JkinocqT4DpQhfhBIuxz5 1xngdwx9Oof29NEKiwRHq0CaZnp9H6rh6HCPvToGxQ8XDbJr+cmbGLjof1YPbPeu2byl vPBYMqYW1rmCeReEjR9Q0vbMYCcQHXy7qDinSXUtsGx9Gwj5JaNAx78BXJ6wej9H4x0v dfUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694195476; x=1694800276; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=BRb6+fsKG46EDKfnC4YLlAaWiUIkKEFKYbSuoOYomDM=; b=mzBkhrTidHdJ5GCFT8M6vJsCGbplw0H+LYqNM1P1QO5YUjJ/IlEqh4tTP3iFhN4U4v hKfNYSkogXPRT/MARseFa6sUjNtT0zd+dcHUwNrDzqqIHlGAiNru+POMc6H7qqtDWqCf DjAT7nbiZ17Qx4Kf/8rVsxqBCQ2RhMm09bV0GCt04d+CO+1mzbX4omZhET2RaPbl0rix /imslqCN6nAk1tAigCOweHgp1greFdBXoLbIlfLnbPr4KB8YiBHjMLJof+ueJszdVwIg RHyG0hEGAzS8vNNZS0C6a0zvBQl06plCcOu03Hu83APUch536wT3wz3AEofxZwYXw2md 8DZw== X-Gm-Message-State: AOJu0YyXproW7K4Q1+k3CI85xXc8C936WW9A8PIrKCrGjrN0AZXqhg2X qS/+VHArLBQHd5Tde3BgaZ7ZaQ== X-Google-Smtp-Source: AGHT+IHDVp7JNs26a0TiyVAh9TOrxhKDOScgayfuGNZ8ybHIPqi1VeFuAio1j+1C4nVFo8ziZdCjmw== X-Received: by 2002:a17:907:2c67:b0:99d:e617:abeb with SMTP id ib7-20020a1709072c6700b0099de617abebmr2178353ejc.23.1694195476339; Fri, 08 Sep 2023 10:51:16 -0700 (PDT) Received: from localhost.localdomain (178-190-168-178.adsl.highway.telekom.at. [178.190.168.178]) by smtp.gmail.com with ESMTPSA id sb5-20020a170906edc500b0099bc0daf3d7sm1323956ejb.182.2023.09.08.10.51.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Sep 2023 10:51:16 -0700 (PDT) Message-ID: <5520a74bc59f5aed4b29772b04c28d58566013a2.camel@cybertec.at> Subject: Re: Even if I have a lot of free space PgSQL returns "ERROR: could not extend file - No space left on device" From: Laurenz Albe To: Nature Conservation Geovista Space , pgsql-novice@lists.postgresql.org Date: Fri, 08 Sep 2023 19:51:15 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 > > =C2=A0 > > 2023-09-08 02:11:23.745 BST [328594] postgres@database ERROR:=C2=A0 cou= ld not extend file "base/16388/7985375.1020": No space left on device > > 2023-09-08 02:11:23.745 BST [328594] postgres@database HINT:=C2=A0 Chec= k free disk space. > > =C2=A0 > > 2023-09-08 02:11:23.745 BST [328594] postgres@database=C2=A0 STATEMENT:= =C2=A0 CREATE TABLE _gaul_administrative_subdivided100 AS ( > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 SELECT *, st_subdivide(geom,100) AS geom_subdivided10= 0=20 > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 FROM = gaul_administrative=20 > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ); >=20 > It seems that it is not a problem of space. [df shows there is space ever= ywhere] "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 the= y are gone again after the statement has failed. Set "temp_file_limit" to avoid that kind of problem. Yours, Laurenz Albe