{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/",
        "slug": "include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory",
        "url": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/"
        },
        "title": "Include external PostgreSQL tablespaces in the cluster dependency inventory",
        "summary": "Keep external tablespace paths with the database cluster recovery inventory.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "continuity-recovery",
            "label": "Continuity & recovery",
            "alt": "Paired infrastructure paths converging on a stable recovered service.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-10-15T13:32:40+00:00",
        "modified_at": "2026-10-15T13:36:15+00:00",
        "reviewed_on": "2026-10-15",
        "reading_minutes": 2,
        "word_count": 246,
        "potentially_affected": "This applies to PostgreSQL 17 storage layout and recovery inventory. It addresses external tablespace dependencies, rather than endorsing manual filesystem-link changes or independent tablespace recovery.",
        "dse_recommendation": "DSE recommends keeping a tablespace map with the cluster's storage and backup records.",
        "primary_source": {
            "name": "PostgreSQL 17 — Tablespaces",
            "url": "https://www.postgresql.org/docs/17/manage-ag-tablespaces.html",
            "published_on": null,
            "authority": "www.postgresql.org"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Keep external tablespace paths with the database cluster recovery inventory.</p>\n<h2>Source facts</h2>\n<p>PostgreSQL 17 tablespaces may live outside the main data directory, but they remain integral parts of the cluster. They depend on metadata in that directory and cannot be attached to another cluster or backed up as autonomous database files. Losing a tablespace can make the cluster unreadable or unable to start. PostgreSQL tracks nondefault tablespace locations through links in pg_tblspc, and the documented location for a new tablespace must be an existing empty directory owned by its operating-system user.</p>\n<p>Source: <a href=\"https://www.postgresql.org/docs/17/manage-ag-tablespaces.html\">PostgreSQL 17 — Tablespaces</a>.</p>\n<h2>Applicability</h2>\n<p>This applies to PostgreSQL 17 storage layout and recovery inventory. It addresses external tablespace dependencies, rather than endorsing manual filesystem-link changes or independent tablespace recovery.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends keeping a tablespace map with the cluster&#8217;s storage and backup records. Include its location, storage owner, intended objects, mount dependency, and recovery destination. Review that map whenever data is moved to a different tier or a mount is retired. Ask the recovery operator to identify every required path before startup. Avoid treating a small main data directory as evidence that most of the database lives safely somewhere else without a corresponding dependency record.</p>\n<h2>Verification</h2>\n<p>Compare the catalog&#8217;s tablespace list with the operating-system paths and backup inventory in a read-only review. Rehearse recovery of the complete cluster with those paths present. Confirm intended objects can be read and document any deliberately remapped locations before accepting the recovered service.</p>\n<h2>Official reference</h2>\n<p><a href=\"https://www.postgresql.org/docs/17/manage-ag-tablespaces.html\">PostgreSQL 17 — Tablespaces</a>. Reviewed October 15, 2026.</p>",
        "content_text": "Keep external tablespace paths with the database cluster recovery inventory.\nSource facts\nPostgreSQL 17 tablespaces may live outside the main data directory, but they remain integral parts of the cluster. They depend on metadata in that directory and cannot be attached to another cluster or backed up as autonomous database files. Losing a tablespace can make the cluster unreadable or unable to start. PostgreSQL tracks nondefault tablespace locations through links in pg_tblspc, and the documented location for a new tablespace must be an existing empty directory owned by its operating-system user.\nSource: PostgreSQL 17 — Tablespaces.\nApplicability\nThis applies to PostgreSQL 17 storage layout and recovery inventory. It addresses external tablespace dependencies, rather than endorsing manual filesystem-link changes or independent tablespace recovery.\nDSE recommendation\nDSE recommends keeping a tablespace map with the cluster’s storage and backup records. Include its location, storage owner, intended objects, mount dependency, and recovery destination. Review that map whenever data is moved to a different tier or a mount is retired. Ask the recovery operator to identify every required path before startup. Avoid treating a small main data directory as evidence that most of the database lives safely somewhere else without a corresponding dependency record.\nVerification\nCompare the catalog’s tablespace list with the operating-system paths and backup inventory in a read-only review. Rehearse recovery of the complete cluster with those paths present. Confirm intended objects can be read and document any deliberately remapped locations before accepting the recovered service.\nOfficial reference\nPostgreSQL 17 — Tablespaces. Reviewed October 15, 2026.",
        "content_markdown": "Keep external tablespace paths with the database cluster recovery inventory.\n\n## Source facts\n\nPostgreSQL 17 tablespaces may live outside the main data directory, but they remain integral parts of the cluster. They depend on metadata in that directory and cannot be attached to another cluster or backed up as autonomous database files. Losing a tablespace can make the cluster unreadable or unable to start. PostgreSQL tracks nondefault tablespace locations through links in pg_tblspc, and the documented location for a new tablespace must be an existing empty directory owned by its operating-system user.\n\nSource: [PostgreSQL 17 — Tablespaces](https://www.postgresql.org/docs/17/manage-ag-tablespaces.html).\n\n## Applicability\n\nThis applies to PostgreSQL 17 storage layout and recovery inventory. It addresses external tablespace dependencies, rather than endorsing manual filesystem-link changes or independent tablespace recovery.\n\n## DSE recommendation\n\nDSE recommends keeping a tablespace map with the cluster’s storage and backup records. Include its location, storage owner, intended objects, mount dependency, and recovery destination. Review that map whenever data is moved to a different tier or a mount is retired. Ask the recovery operator to identify every required path before startup. Avoid treating a small main data directory as evidence that most of the database lives safely somewhere else without a corresponding dependency record.\n\n## Verification\n\nCompare the catalog’s tablespace list with the operating-system paths and backup inventory in a read-only review. Rehearse recovery of the complete cluster with those paths present. Confirm intended objects can be read and document any deliberately remapped locations before accepting the recovered service.\n\n## Official reference\n\n[PostgreSQL 17 — Tablespaces](https://www.postgresql.org/docs/17/manage-ag-tablespaces.html). Reviewed October 15, 2026."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/",
                "url": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-10-15"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Include external PostgreSQL tablespaces in the cluster dependency inventory",
                        "item": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/#article",
                "identifier": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/",
                "url": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/",
                "headline": "Include external PostgreSQL tablespaces in the cluster dependency inventory",
                "description": "Keep external tablespace paths with the database cluster recovery inventory.",
                "abstract": "Keep external tablespace paths with the database cluster recovery inventory.",
                "articleBody": "Keep external tablespace paths with the database cluster recovery inventory.\nSource facts\nPostgreSQL 17 tablespaces may live outside the main data directory, but they remain integral parts of the cluster. They depend on metadata in that directory and cannot be attached to another cluster or backed up as autonomous database files. Losing a tablespace can make the cluster unreadable or unable to start. PostgreSQL tracks nondefault tablespace locations through links in pg_tblspc, and the documented location for a new tablespace must be an existing empty directory owned by its operating-system user.\nSource: PostgreSQL 17 — Tablespaces.\nApplicability\nThis applies to PostgreSQL 17 storage layout and recovery inventory. It addresses external tablespace dependencies, rather than endorsing manual filesystem-link changes or independent tablespace recovery.\nDSE recommendation\nDSE recommends keeping a tablespace map with the cluster’s storage and backup records. Include its location, storage owner, intended objects, mount dependency, and recovery destination. Review that map whenever data is moved to a different tier or a mount is retired. Ask the recovery operator to identify every required path before startup. Avoid treating a small main data directory as evidence that most of the database lives safely somewhere else without a corresponding dependency record.\nVerification\nCompare the catalog’s tablespace list with the operating-system paths and backup inventory in a read-only review. Rehearse recovery of the complete cluster with those paths present. Confirm intended objects can be read and document any deliberately remapped locations before accepting the recovered service.\nOfficial reference\nPostgreSQL 17 — Tablespaces. Reviewed October 15, 2026.",
                "datePublished": "2026-10-15T13:32:40+00:00",
                "dateModified": "2026-10-15T13:36:15+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/include-external-postgresql-tablespaces-in-the-cluster-dependency-inventory/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Include external PostgreSQL tablespaces in the cluster dependency inventory"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 246,
                "timeRequired": "PT2M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "PostgreSQL 17 — Tablespaces",
                    "url": "https://www.postgresql.org/docs/17/manage-ag-tablespaces.html"
                }
            }
        ]
    }
}