Skip to content

PostgreSQL Specific Notes

Jump to bottom
Tim Kirschke edited this page Mar 20, 2024 · 1 revision

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.

Table of Content

  1. Staging
    1. Prejoining
    2. Derived Columns
    3. Add new columns to Hashdiff
  2. DV-Entities
    1. Hubs
      1. Standard Hub
    2. Links
      1. Standard Link
      2. Non-Historized Link
      3. Dependent Child Keys
    3. Satellites
      1. Standard Satellite
        1. Standard Satellite v0
        2. Standard Satellite v1
      2. Multi-Active Satellite
        1. Multi-Active Satellite v0
        2. Multi-Active Satellite v1
      3. Record-Tracking Satellite
      4. Non-Historized Satellite
    4. Reference Data
      1. Reference Hub
      2. Reference Satellite
        1. Reference Satellite v0
        2. Reference Satellite v1
      3. Reference Tables
    5. Business Vault
      1. PIT
        1. Hook Cleanup PITs
      2. Snapshot Control
        1. Snapshot Control v0
        2. Snapshot Control v1
  3. General
    1. Global Variables
    2. Multi-Source Entites
    3. How To Track Effectivity
    4. The rsrc_static Attribute
    5. Testing a Data Vault
    6. Adaper Specific Notes
      1. RedShift
      2. PostgeSQL
      3. Exasol
      4. Synapse
      5. Databricks
Clone this wiki locally