https://www.postgresscripts.com/tags/tablespaces/Recent content in Tablespaces on Postgres ScriptsHugo -- gohugo.ioenPostgresScripts.comFri, 03 Jul 2026 00:00:00 +0000https://www.postgresscripts.com/post/query-postgresql-tablespace-info-pg-tablespace/Fri, 03 Jul 2026 00:00:00 +0000https://www.postgresscripts.com/post/query-postgresql-tablespace-info-pg-tablespace/ <h2 id="query-postgresql-tablespace-info-with-pg_tablespace">Query PostgreSQL Tablespace Info with pg_tablespace</h2> <p>What tablespaces exist in this cluster, who owns each one, and where do their files actually live on disk? <code>pg_tablespace</code> answers all three: it holds one row per tablespace with the owner OID, access control list, storage options, and — via <code>pg_tablespace_location()</code> — the on-disk path, all readable from a single catalog query without parsing configuration files or tracing symlinks by hand.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-1012089347386563" data-ad-slot="7945792173" data-ad-format="auto" data-full-width-responsive="true"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p>Tablespaces are PostgreSQL's mechanism for controlling where data files land on disk. Every cluster starts with two built-in spaces: <code>pg_default</code>, which holds user tables and indexes, and <code>pg_global</code>, which holds the cluster-wide system catalogs. Additional tablespaces appear when a DBA runs <code>CREATE TABLESPACE</code> pointing at a different mount point — typically a faster SSD volume for a hot OLTP schema, a slower spinning disk for archive data, or a dedicated volume to isolate write-amplification from MVCC-heavy tables.</p>