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 1qg2oM-00EFFr-NT for pgsql-novice@arkaria.postgresql.org; Tue, 12 Sep 2023 12:48:10 +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 1qg2oK-008XRS-TK for pgsql-novice@arkaria.postgresql.org; Tue, 12 Sep 2023 12:48:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qg2oK-008XRB-FB for pgsql-novice@lists.postgresql.org; Tue, 12 Sep 2023 12:48:08 +0000 Received: from mail-lf1-x130.google.com ([2a00:1450:4864:20::130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qg2oG-004eX7-Pz for pgsql-novice@lists.postgresql.org; Tue, 12 Sep 2023 12:48:07 +0000 Received: by mail-lf1-x130.google.com with SMTP id 2adb3069b0e04-502a7e1bdc7so5374790e87.0 for ; Tue, 12 Sep 2023 05:48:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1694522884; x=1695127684; 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=OPlgXlT71I6hitn4SGNQtwogOb1kQnD80ZtKjutAIV8=; b=IgZgGUUZeh2td6AT/FY6DCsDElyRi3FPkQxuYdu4Gl00H9126+IlECGA+L7OPaLpci nqHKSYHqzf1uC1sDS15qyFJSHP+BG9PiHi4phttp7lUS/UDvTFMQRZHiDNHdHflvmUs6 splPlAZLVNgmqpXhQzUIffdO66RURxFLj6tTGbUMvDNvGNBRsamW3UcN7EnuzMqOwU7I 5pb5Sf5aGXy2h9r3UHaZvGoxh8pU/l+J5DoQFFcHR1AITIF9sOyxoJb5HN9mKe+3/mSh VRRagTwgBRaUBEzC42LZm+Z5fA28wzE3GaVF4v/p6CROqxJiVaHWg697vKCuOByg6blu UKOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694522884; x=1695127684; 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=OPlgXlT71I6hitn4SGNQtwogOb1kQnD80ZtKjutAIV8=; b=qCu+55JppHHL/aCd9u0eC79WVPPBh2CANI2aGkMUvhlQbCcOcTIw7k6OwCkmLlnjCd e4yT24cmUlnjnoaThNMCUbPhdGIKDrn5LX0K8DFRBjzEdY/25OGFKOTzAOjDXgIYW3Nk 9185EDl5mrj3cHw+e6Ybbf1AqSYkl9r7SOb5lDFQa6OmVFXoWZrZHVFXNZVzu4ItL27E Zht5dWblDRswtUjDjqRP5a5j5xhrJZcVGmUhrZTD828Swc1qczSEqYNJsEk0NGr7zbvM I1gbRHBVbSTXcPpgVqLAqgh/WSc8D3RbEt9pSHCzMZR0pMVX+FfWKC+DM9SJjrszc+5i 8b5w== X-Gm-Message-State: AOJu0YwHU0PRqLzYucgo3OyutHevHsuR22K2kG9EkEWpyC0bqRFMwNnz Wjnm8OhubwgoZwFUStmZ3/Qg8WapTvF05awe3Dw= X-Google-Smtp-Source: AGHT+IHdwA4cXOqW20FAcFl5zqD8jIOYYwfkV4KSaN1OYXtvcpLcMQICRWIxp2ZPuzjSAeWIVKmjrQ== X-Received: by 2002:a05:6512:10d1:b0:500:86cf:1249 with SMTP id k17-20020a05651210d100b0050086cf1249mr11654907lfg.61.1694522883675; Tue, 12 Sep 2023 05:48:03 -0700 (PDT) Received: from localhost.localdomain (178-190-169-82.adsl.highway.telekom.at. [178.190.169.82]) by smtp.gmail.com with ESMTPSA id dy24-20020a05640231f800b00523a43f9b1dsm5822797edb.22.2023.09.12.05.48.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Sep 2023 05:48:03 -0700 (PDT) Message-ID: <753193ede36dad1b9da0755e17d69f4980bb3333.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: Tue, 12 Sep 2023 14:48:02 +0200 In-Reply-To: References: <5520a74bc59f5aed4b29772b04c28d58566013a2.camel@cybertec.at> 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 Tue, 2023-09-12 at 13:12 +0100, Nature Conservation Geovista Space wrote= : > On Sat, 9 Sept 2023 at 03:54, Laurenz Albe wro= te: > > On Fri, 2023-09-08 at 16:01 -0400, bruno da silva wrote: > > > Hello. Does temp_file_limt also applies to reindex? > >=20 > > To the extent that REINDEX creates temporary files, yes. > > It will limit the size of temporary files created when the > > rows are sorted. > >=20 > > It does *not* limit the size of the data files for the new > > index. > > 1 - At the moment my postgresql.conf is by default with no limit #temp_= file_limit =3D -1 > Maybe I just have to uncomment it so that this rule really applies. Let's= see this evening if > your suggestion fix it. "-1" meanse "no limit", so removing the comment won't do anything. You also have to change the value. > 2 - Do you think it could come from another param not set up correctly? "work_mem" influences the amount of temp files required. But if your query needs enough temp files to fill your disk, higher settings of "work_mem" ar= e unlikely to fix that. > 3 - Can I try to watch out the log or size of the temporary table created= after my query failed > so that I can investigate what happened? Sure. Set "log_temp_files =3D '100kB'", and every temp file above that siz= e will be logged. Yours, Laurenz Albe