Message-ID: <e55acd6eb1b237f1293b0150f60e1655a8778724.camel@cybertec.at>
Subject: Re: Size of /pgdata
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Raj <rajeshkumar.dba09@gmail.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Sun, 14 Jun 2026 21:30:00 +0200
In-Reply-To: 
 <CAJk5Atb1v7=x-wsS-tL7Lxs7yXQy8Ng-GhXG+zzZ1gVAx=Xzjw@mail.gmail.com>
References: 
	<CAJk5Atb1v7=x-wsS-tL7Lxs7yXQy8Ng-GhXG+zzZ1gVAx=Xzjw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/e55acd6eb1b237f1293b0150f60e1655a8778724.camel%40cybertec.at>
Precedence: bulk

On Sat, 2026-06-13 at 12:18 +0530, Raj wrote:
> I took one big sample table which is 73GB, and using relfilenode(327683) =
I tried finding the
> underlying file size du -sh 327683*=C2=A0 and able to find the total size=
 the files occpuing and
> found 113gb.......so for one table itself it is 40Gb additional...

Investigate more:

- Make sure that you don't get files from another filenode like 3276838.

- If the relation (as shown by pg_relation_size('tablename')) is 73GB,
  it should consist of 327683, 327683.1, 327683.2, ..., 327683.72.
  Check what additional files there are.

- Extra files can be left behind after a crash.  Were there any?

Yours,
Laurenz Albe