Re: Available disk space per tablespace

From: harrisontbooth(at)gmail(dot)com
To: Christoph Berg <myon(at)debian(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Available disk space per tablespace
Date: 2026-10-13 17:17:15
Message-ID: CAAH-eSXRXv+1+PqxcqZxw6QSuq7LVaxHAbLsJuUBaZ8mtN32Ng@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

V7 passes the tested Windows SQL and psql cases on native ARM64 and
emulated x64.

Both pg_tablespace_avail variants agree with independent
GetDiskFreeSpaceExW samples for pg_default, pg_global and a custom
path containing spaces. Before/after samples use a 64MB tolerance for
concurrent changes.

Default/custom access, CREATE grants, pg_read_all_stats membership and
missing name/OID diagnostics pass. Actual psql \db+ shows Free and No
Access as expected.

Full integration builds and setup groups pass; the checkout includes
earlier Windows changes. All tested paths share one NTFS volume.
Quotas, different volumes and older-server psql compatibility weren't
tested. The disposable clusters were stopped and custom tablespaces
dropped.

Happy to provide the script and samples.

Original discussion:
https://www.postgresql.org/message-id/CAF0whue1Vn-BiMRD3Kw0B5QQRgZXukXdCvkm8TmVycx5bj0WVA@mail.gmail.com

Best,

Harrison

Attachment Content-Type Size
06-tablespace-availability-evidence.zip application/zip 20.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-13 17:17:21 Re: Partition-aware simplification of constant IN lists after partition pruning
Previous Message Tom Lane 2026-10-13 16:56:44 Re: [PG19] jsonb_object_agg as a window function returns stale values