| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Fix invalid value of pg_aios.pid, function pg_get_aios() |
| Date: | 2026-03-23 09:15:20 |
| Message-ID: | E1w4bNX-0013nE-0o@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix invalid value of pg_aios.pid, function pg_get_aios()
When the value of pg_aios.pid is found to be 0, the function had the
idea to set "nulls" to "false" instead of "true", without setting the
value stored in the tuplestore. This could lead to the display of buggy
data. The intention of the code is clearly to display NULL when a PID
of 0 is found, and this commit adjusts the logic to do so.
Issue introduced by 60f566b4f243.
Author: ChangAo Chen <cca5507(at)qq(dot)com>
Reviewed-by: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Discussion: https://postgr.es/m/tencent_7D61A85D6143AD57CA8D8C00DEC541869D06@qq.com
Backpatch-through: 18
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/93b76db0ace674a29a5d2146a139d6dd87b99659
Modified Files
--------------
src/backend/storage/aio/aio_funcs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2026-03-23 10:35:28 | pgsql: Fix multixact backwards-compatibility with CHECKPOINT race condi |
| Previous Message | Peter Eisentraut | 2026-03-23 07:44:53 | pgsql: ci: Run headerscheck and cpluspluscheck in parallel |