diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-06-07 15:34:30 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-06-07 15:34:30 -0400 |
| commit | bf4717b0910763e81ffbf0358de06a88faee5132 (patch) | |
| tree | 9f6deed5441c22cfde473a15b8a2157a5cb2432c | |
| parent | 51da231597a9e414174cf621b219559e18269dc3 (diff) | |
| download | postgresql-bf4717b0910763e81ffbf0358de06a88faee5132.tar.gz postgresql-bf4717b0910763e81ffbf0358de06a88faee5132.zip | |
Fix off-by-one loop termination condition in pg_stat_get_subscription().
pg_stat_get_subscription scanned one more LogicalRepWorker array entry
than is really allocated. In the worst case this could lead to SIGSEGV,
if the LogicalRepCtx data structure is near the end of shared memory.
That seems quite unlikely though (thanks to the ordering of calls in
CreateSharedMemoryAndSemaphores) and we've heard no field reports of it.
A more likely misbehavior is one row of garbage data in the function's
result, but even that is not real likely because of the check that the
pid field matches some live backend.
Report and fix by Kuntal Ghosh. This bug is old, so back-patch
to all supported branches.
Discussion: https://postgr.es/m/CAGz5QCJykEDzW6jQK6Yz7Qh_PMtD=95de_7QoocbVR2Qy8hWZA@mail.gmail.com
| -rw-r--r-- | src/backend/replication/logical/launcher.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/replication/logical/launcher.c b/src/backend/replication/logical/launcher.c index bd5f78cf9a2..2bdab53e19b 100644 --- a/src/backend/replication/logical/launcher.c +++ b/src/backend/replication/logical/launcher.c @@ -935,7 +935,7 @@ pg_stat_get_subscription(PG_FUNCTION_ARGS) /* Make sure we get consistent view of the workers. */ LWLockAcquire(LogicalRepWorkerLock, LW_SHARED); - for (i = 0; i <= max_logical_replication_workers; i++) + for (i = 0; i < max_logical_replication_workers; i++) { /* for each row */ Datum values[PG_STAT_GET_SUBSCRIPTION_COLS]; |