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 1qg2HE-00ECt4-Qh for pgsql-novice@arkaria.postgresql.org; Tue, 12 Sep 2023 12:13:56 +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 1qg2GF-008CtA-DC for pgsql-novice@arkaria.postgresql.org; Tue, 12 Sep 2023 12:12:55 +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 1qg2GF-008Csu-0i for pgsql-novice@lists.postgresql.org; Tue, 12 Sep 2023 12:12:54 +0000 Received: from mail-lf1-x12d.google.com ([2a00:1450:4864:20::12d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qg2GB-00491a-SI for pgsql-novice@lists.postgresql.org; Tue, 12 Sep 2023 12:12:53 +0000 Received: by mail-lf1-x12d.google.com with SMTP id 2adb3069b0e04-50091b91a83so9084265e87.3 for ; Tue, 12 Sep 2023 05:12:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694520769; x=1695125569; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=x7NrEFBEfnkdCNl3nlOBFC9T6dVrHH04zsDVN78RfNg=; b=hFT60n5WI8qyguew6aGo8EiApYBFhK2LRl3mqrufkea0Ou4MLBLGt2PLy9Bmpgki9h 3oC/1vvefiNQoqn8rxoczhOj3aKNNj3TANegsVl1f5dh5UUHctZ74nq17dM7fZsEWEeG wlVGMFbfj+U69KwhKPVeSFr2TR45Ly0Siv2FA8aNmDIHS+1xVhGOYDQsDqdkmaNwwhPw GniWArgYI4YTbTwh0XEbmMKthwbfKFxBF9alW2ilh+QUpwuV+3dTCsyWo66qw7apABeh IcPPjH95oxSUPX6NTfSdzd2ra4hzGXW84tUWDx+td+I2mdl/+8g7Fldzy+4FI04oIiDv rKyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694520769; x=1695125569; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=x7NrEFBEfnkdCNl3nlOBFC9T6dVrHH04zsDVN78RfNg=; b=JCMwd/Yk+EM4vcAvMMb/bbjS6H6o7kSkPLzhJIIehkfSemkouoyZoKZ0jjWwRNG74C lUMRyyMA36hdS8AgFesSbA8RCrJqrw3sawtYewjdyBkJ1VEUuqGqIAz8TIDttdo8l3St w+d5DqLpN8mIOtB7sSlF4UPBnP88ohDN5cHsjyIOQW7f/thD4uvLa9wHHkBRlfZIZ/Nj kQlLQnCRWyRDi4UoBpqxmTv1gUb8MVB1POOP7vuyqsAwIKZRf/QxhKDNyPwqD5jVH1cE 3M+NCm/6P5FuM2RUoOvRuB+Y/hAa31Hzd1fafCTLkswxvW/56HnWxcLZG1Ne6vBqolIP 4lyg== X-Gm-Message-State: AOJu0YzF2D+5uU3daHXJcLlOhpfURWM3HAXlTOTdHOMhodjy4/5zMJfZ +p8xlNZ3MohfWvuf5518aay4jn7jc6dyc9jQnyhQg1YjUHbUOg== X-Google-Smtp-Source: AGHT+IE4ksiTXM6DjUm9r9U2r7sRbxl7Y59lxdQkU9v6c1kcuETaVrCHXrknDsKkg0Kc5Ta3WaPOhFtuQ9QZS/sW/4Q= X-Received: by 2002:ac2:4bcf:0:b0:500:bddc:56d5 with SMTP id o15-20020ac24bcf000000b00500bddc56d5mr11076897lfq.37.1694520768869; Tue, 12 Sep 2023 05:12:48 -0700 (PDT) MIME-Version: 1.0 References: <5520a74bc59f5aed4b29772b04c28d58566013a2.camel@cybertec.at> In-Reply-To: From: Nature Conservation Geovista Space Date: Tue, 12 Sep 2023 13:12:37 +0100 Message-ID: Subject: Re: Even if I have a lot of free space PgSQL returns "ERROR: could not extend file - No space left on device" To: pgsql-novice@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000007e3c5b0605285cd3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007e3c5b0605285cd3 Content-Type: text/plain; charset="UTF-8" Hi Laurenz, Thanks a lot for your kind support. 1 - At the moment my *postgresql.conf *is by default with no limit *#temp_file_limit = -1* Maybe I just have to uncomment it so that this rule really applies. Let's see this evening if your suggestion fix it. 2 - Do you think it could come from another param not set up correctly? 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? Cheers, Vincent On Sat, 9 Sept 2023 at 03:54, Laurenz Albe wrote: > On Fri, 2023-09-08 at 16:01 -0400, bruno da silva wrote: > > Hello. Does temp_file_limt also applies to reindex? > > To the extent that REINDEX creates temporary files, yes. > It will limit the size of temporary files created when the > rows are sorted. > > It does *not* limit the size of the data files for the new > index. > > Yours, > Laurenz Albe > --0000000000007e3c5b0605285cd3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Laurenz,=C2=A0

Thanks a lot for your= kind support.

1 - At the moment my=C2=A0postgr= esql.conf=C2=A0is by default with no limit=C2=A0 =C2=A0#temp_file_li= mit =3D -1
Maybe I just have to uncomment it so that this rule real= ly applies. Let's see this evening if your suggestion fix it.
=

2 - Do you think it could come from another param not s= et up correctly?

3 - Can I try to watch out the lo= g or size of the temporary table created after my query failed so that=C2= =A0I can investigate what happened?

Cheers,<= /div>

Vincent

=
On Sat, 9 Sept 2023 at 03:54, Laurenz= Albe <laurenz.albe@cybertec= .at> wrote:
On Fri, 2023-09-08 at 16:01 -0400, bruno da silva wrote:
> Hello. Does temp_file_limt also applies to reindex?

To the extent that REINDEX creates temporary files, yes.
It will limit the size of temporary files created when the
rows are sorted.

It does *not* limit the size of the data files for the new
index.

Yours,
Laurenz Albe
--0000000000007e3c5b0605285cd3--