| From: | David Rowley <drowley(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Add missing TidRangePath handling in print_path() |
| Date: | 2023-09-28 11:04:23 |
| Message-ID: | E1qlooh-006S3V-QI@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Add missing TidRangePath handling in print_path()
Tid Range scans were added back in bb437f995. That commit forgot to add
handling for TidRangePaths in print_path().
Only people building with OPTIMIZER_DEBUG might have noticed this, which
likely is the reason it's taken 4 years for anyone to notice.
Author: Andrey Lepikhov
Reported-by: Andrey Lepikhov
Discussion: https://postgr.es/m/379082d6-1b6a-4cd6-9ecf-7157d8c08635@postgrespro.ru
Backpatch-through: 14, where bb437f995 was introduced
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/9861fe2cdd0216f6e25377cab3b95fccd854de84
Modified Files
--------------
src/backend/optimizer/path/allpaths.c | 3 +++
1 file changed, 3 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-09-28 13:38:28 | pgsql: doc: Clarify where ereport severity levels are defined |
| Previous Message | David Rowley | 2023-09-28 11:03:53 | pgsql: Add missing TidRangePath handling in print_path() |