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 1syXgr-000eyW-0J for pgsql-general@arkaria.postgresql.org; Wed, 09 Oct 2024 14:29:25 +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 1syXgq-002B2M-4T for pgsql-general@arkaria.postgresql.org; Wed, 09 Oct 2024 14:29:24 +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 1syXgp-002B2E-Qf for pgsql-general@lists.postgresql.org; Wed, 09 Oct 2024 14:29:24 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1syXgn-000Am1-30 for pgsql-general@lists.postgresql.org; Wed, 09 Oct 2024 14:29:23 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-2883c77eb8fso261133fac.1 for ; Wed, 09 Oct 2024 07:29:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728484160; x=1729088960; 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=7f7xRgEO629v4c1O8l6KaOA1MHekl19cxPtAoQAeFeQ=; b=S58ff6uGSMV2PNJPUJwaI+Eb5hyhHOEAcJUBKwnTW6c9HkMZCWohfwHuk5GDiHjtwh R23F/cZQNZp0tCFJYKSRjYjZw/clzEtXZsYxLfMgTRNMuBbvlgOxaWOOr8UOpwP6dEfI UkKK+qReIzDnWnLaTqIppQK9k+frm84QgN6uVrKeemt87FdJogB+2/sGP7jkOqc4wXh/ I7vIZHoAqGL84kpHwxyV93n9aNGpIFkXnpN2Q/GeJAQadLkP+7tJuGk89OK4YnLGIVH6 n/m/YRl/9Q8jThaHE7z7J6IXwC+GLzMPFXGskXLd4In5xKwB/aNc9cxYBQ7Dq8QHUuIl Iqhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728484160; x=1729088960; 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=7f7xRgEO629v4c1O8l6KaOA1MHekl19cxPtAoQAeFeQ=; b=pkr7i7Yv/2DCA2BrFxU5MEa12y01JhWd7CQ6RMgN3dbKPaOTEEEcqXdNsJkHMHlwys d8gK5TzhAq8TwfUho7X/IWOGn2tMCMWQvTlJQZVU/1g8LgXaaaqpSqbGkY5+lqgsowXB sZyAwp/15wjIpdEwzPSWUpqQFlVSPle0RbDy5k1jYd54A3FyYVCYu5ToK4Ryjla3aaeX HnIb9cXyvrmVG7pfzi7mL6MyNiLf4k7NVnFLn7ppw2+DUw1tzCteGsMH44qMX/plwr1N b9u307rcy6svgyvAJzfb6dCrd84n8U+c/t57y7MlEdWokTH6rWqoncNqP7LmiXjqauSq 6f9Q== X-Gm-Message-State: AOJu0Yzxh3CS3SX6EPwyNt/cvyWoFwoa1vGKMt3BRgME7yG2SbGC7e1m 6GZYh4kW6V62vLNqDDXxrtPgDKGFERIQueilnJmphbyT0N7bqrh5LSTHEo48HWTZfNZXpsuehC6 fGKAFOsaRZCGB37J1IksPzrhCtH+czw== X-Google-Smtp-Source: AGHT+IE67MbAg8p8XoHFE5mLWjwmfe+1GrGx30D4Vs3mOLz4Q/Edir89Wv2ZmLVRxLlaeS3R/gTrPWOBrY6EX6PC4FU= X-Received: by 2002:a05:6871:586:b0:288:18a0:e169 with SMTP id 586e51a60fabf-288342d1ce2mr1880901fac.19.1728484160265; Wed, 09 Oct 2024 07:29:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 9 Oct 2024 10:29:09 -0400 Message-ID: Subject: Re: Disk is filling up with large files. How can I clean? To: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000005f668406240c14d2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005f668406240c14d2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Oct 9, 2024 at 9:02=E2=80=AFAM Philip Semanchuk < philip@americanefficient.com> wrote: > > > On Oct 9, 2024, at 5:52=E2=80=AFAM, Torsten F=C3=B6rtsch > wrote: > > > > Filenames like 16665, 16665.1, 16665.2 etc all represent the same table > (or similar). The number 16665 is called the file node. > > > > To get a list of file nodes for a specific database you can run: > > > > SELECT oid::regclass::text, relfilenode FROM pg_class; > > > > The /16384/ in the path represents the database. To decipher that you > can run: > > > > SELECT datname, oid FROM pg_database; > > > > Once you have all that information, you know which database to connect > to and which tables are big. Then you can DROP/DELETE/TRUNCATE or so. > > Mikael, if you=E2=80=99re unaware of VACUUM FULL (as opposed to just VACU= UM), you > should read about that too. > VACUUM FULL with an almost-full disk probably isn't the wisest idea. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. crustacean! --0000000000005f668406240c14d2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Oct 9, 2024 at 9:02=E2=80=AFAM Ph= ilip Semanchuk <philip@a= mericanefficient.com> wrote:

> On Oct 9, 2024, at = 5:52=E2=80=AFAM, Torsten F=C3=B6rtsch <tfoertsch123@gmail.com> wrote:
>
> Filenames like 16665, 16665.1, 16665.2 etc all represent the same tabl= e (or similar). The number 16665 is called the file node.
>
> To get a list of file nodes for a specific database you can run:
>
> SELECT oid::regclass::text, relfilenode FROM pg_class;
>
> The /16384/ in the path represents the database. To decipher that you = can run:
>
> SELECT datname, oid FROM pg_database;
>
> Once you have all that information, you know which database to connect= to and which tables are big. Then you can DROP/DELETE/TRUNCATE or so.

Mikael, if you=E2=80=99re unaware of VACUUM FULL (as opposed to just VACUUM= ), you should read about that too.

VACU= UM FULL with an almost-full disk probably isn't the wisest idea.
<= div>
--
Death to <Reda= cted>, and butter sauce.
Don't boil me, I'm still alive.
=
<Redacted> crustacean!
--0000000000005f668406240c14d2--