summaryrefslogtreecommitdiff
path: root/src/backend/backup/basebackup_sink.c
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2025-09-19 05:38:40 +0000
committerAmit Kapila <akapila@postgresql.org>2025-09-19 05:38:40 +0000
commit5b148706c5c8ffffe5662fe569a0f0bcef2351d9 (patch)
tree957ed0d501fbbff5c70382f1f98819b9be6608f9 /src/backend/backup/basebackup_sink.c
parent8aac5923a3611aa89998368a09c54892b93ebdd9 (diff)
Add optional pid parameter to pg_replication_origin_session_setup().
Commit 216a784829c introduced parallel apply workers, allowing multiple processes to share a replication origin. To support this, replorigin_session_setup() was extended to accept a pid argument identifying the process using the origin. This commit exposes that capability through the SQL interface function pg_replication_origin_session_setup() by adding an optional pid parameter. This enables multiple processes to coordinate replication using the same origin when using SQL-level replication functions. This change allows the non-builtin logical replication solutions to implement parallel apply for large transactions. Additionally, an existing internal error was made user-facing, as it can now be triggered via the exposed SQL API. Author: Doruk Yilmaz <doruk@mixrank.com> Author: Hayato Kuroda <kuroda.hayato@fujitsu.com> Reviewed-by: Amit Kapila <amit.kapila16@gmail.com> Reviewed-by: Euler Taveira <euler@eulerto.com> Discussion: https://postgr.es/m/CAMPB6wfe4zLjJL8jiZV5kjjpwBM2=rTRme0UCL7Ra4L8MTVdOg@mail.gmail.com Discussion: https://postgr.es/m/CAE2gYzyTSNvHY1+iWUwykaLETSuAZsCWyryokjP6rG46ZvRgQA@mail.gmail.com
Diffstat (limited to 'src/backend/backup/basebackup_sink.c')
0 files changed, 0 insertions, 0 deletions