| From: | solai v <solai(dot)cdac(at)gmail(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org> |
| Cc: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Quan Zongliang <quanzongliang(at)yeah(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Available disk space per tablespace |
| Date: | 2026-07-28 09:35:09 |
| Message-ID: | CAF0whue1Vn-BiMRD3Kw0B5QQRgZXukXdCvkm8TmVycx5bj0WVA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Christoph,
I tested the latest v7 patch on Linux.
The patch applied and built without any issues. After rebuilding
PostgreSQL and re-running initdb, I verified the new functionality.
I tested both the name and oid variants of pg_tablespace_avail(),
confirmed that the new Free column in \db+ displays the expected
values, and compared the reported free space with df -h, which matched
as expected. I also created a custom tablespace and verified that it
reports the available space correctly.
In addition, I tested the behavior with a non-superuser account to
verify the permission handling, and everything worked as expected.
Finally, I ran:
make check TESTS=tablespace
The tablespace regression test passed successfully, and I also ran the
full regression test suite, which completed with all tests passing.
Overall, the v7 changes worked well in my testing, and I didn't
encounter any issues.
Regards,
Solai
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yugo Nagata | 2026-07-28 09:43:13 | Re: enhance wraparound warnings |
| Previous Message | Chao Li | 2026-07-28 09:23:33 | Re: Fix RETURNING side effects for FOR PORTION OF leftover rows |