Re: Adding a LogicalRepWorker type field
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>
Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-08-09T06:18:06Z
Lists: pgsql-hackers
On Tue, Aug 8, 2023 at 1:39 PM Peter Smith <smithpb2250@gmail.com> wrote: > > On Fri, Aug 4, 2023 at 5:45 PM Peter Smith <smithpb2250@gmail.com> wrote: > > v4-0001 uses only 3 simple inline functions. Callers always pass > parameters as Bharath had suggested. > * - Assert(am_leader_apply_worker()); + Assert(is_leader_apply_worker(MyLogicalRepWorker)); ... - if (am_leader_apply_worker()) + if (is_leader_apply_worker(MyLogicalRepWorker)) Passing everywhere MyLogicalRepWorker not only increased the code change footprint but doesn't appear any better to me. Instead, let am_parallel_apply_worker() keep calling isParallelApplyWorker(MyLogicalRepWorker) as it is doing now. I feel even if you or others feel that is a better idea, we can debate it separately after the main patch is done because as far as I understand that is not the core idea of this proposal. * If you do the above then there won't be a need to change the variable name is_parallel_apply_worker in logicalrep_worker_launch. -- With Regards, Amit Kapila.
Commits
-
Simplify the logical worker type checks by using the switch on worker type.
- 1cdc6d86bfc3 17.0 landed
-
Simplify determining logical replication worker types.
- 2a8b40e36819 17.0 landed