pgsql: Honor run_as_owner option in tablesync worker.

From: Masahiko Sawada <msawada(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Honor run_as_owner option in tablesync worker.
Date: 2023-06-09 01:44:12
Message-ID: E1q7RAi-000qlR-0s@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Honor run_as_owner option in tablesync worker.

Commit 482675987 introduced "run_as_owner" subscription option so that
subscription runs with either the permissions of the subscription
owner or the permission of the table owner. However, tablesync workers
did not use this option for the initial data copy.

With this change, tablesync workers run with appropriate permissions
based on "run_as_owner" option.

Ajin Cherian, with changes and regression tests added by me.

Reported-By: Amit Kapila
Author: Ajin Cherian, Masahiko Sawada
Reviewed-by: Ajin Cherian, Amit Kapila
Discussion: https://postgr.es/m/CAA4eK1L=qzRHPEn+qeMoKQGFBzqGoLBzt_ov0A89iFFiut+ppA@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/a83edeaf684a70da02fa2bce8b7e3aefa3f906f5

Modified Files
--------------
src/backend/replication/logical/tablesync.c | 64 ++++++++++++++---------
src/test/subscription/t/033_run_as_table_owner.pl | 38 +++++++++++++-
2 files changed, 75 insertions(+), 27 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2023-06-09 02:57:20 pgsql: Refactor routine to find single log content pattern in TAP tests
Previous Message Michael Paquier 2023-06-09 00:38:04 pgsql: Refactor log check logic for connect_ok/fails in PostgreSQL::Tes