| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Raj <rajeshkumar(dot)dba09(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Size of /pgdata |
| Date: | 2026-06-14 19:30:00 |
| Message-ID: | e55acd6eb1b237f1293b0150f60e1655a8778724.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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* 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raj | 2026-06-15 01:18:23 | Re: Size of /pgdata |
| Previous Message | Michael Grimm | 2026-06-14 11:36:42 | Cluster of 3 instances in distinct datacenters |