Skip to content
DataVault4dbt
Home FAQ Documentation Support Get Started
  • Macro Instructions
    • Staging
      • Prejoining
      • Derived Columns
      • Add new columns to Hashdiff
    • Hubs
      • Standard Hub
    • Links
      • Standard Link
      • Non-Historized Link
      • Dependent Child Keys
    • Satellites
      • Standard Satellite
        • Standard Satellite v0
        • Standard Satellite v1
      • Multi-Active Satellite
        • Multi-Active Satellite v0
        • Multi-Active Satellite v1
      • Effectivity Satellite
      • Record-Tracking Satellite
      • Non-Historized Satellite
    • Reference Data
      • Reference Hub
      • Reference Satellite
        • Reference Satellite v0
        • Reference Satellite v1
      • Reference Tables
    • Business Vault
      • PIT
        • Hook Cleanup PITs
      • Snapshot Control
        • Snapshot Control v0
        • Snapshot Control v1
  • General Usage Notes
    • Defining Macro Parameter
    • Global Variables
    • Multi-Source Entites
    • How To Track Effectivity
    • The rsrc_static Attribute
    • Adapter Specific Notes
      • Redshift
      • PostgreSQL
      • Exasol
      • Synapse
      • Oracle
      • Databricks
    • Testing a Data Vault

talk to an expert


DataVault4dbt / Documentation / General Usage Notes / Adapter Specific Notes / PostgreSQL

PostgreSQL

Satellite Splits

By default, PostgreSQL sets the Function Arguments (MAX_FUNCTION_ARGUMENTS) to 100, which imposes a limitation of 50 columns per satellite when the server sticks to default settings. To accommodate more columns for a satellite in PostgreSQL, you’ll need to adjust the database server settings or opt for more frequent satellite splits. This adjustment becomes necessary to manage larger sets of columns effectively within the satellites.

DataVault4dbt - © 2024 Scalefree International GmbH

Imprint | Privacy Policy | Terms and Conditions