clean up pid_t printing and get rid of pgpid_t
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-10-10T08:57:21Z
Lists: pgsql-hackers
Attachments
- v2-0001-doc-Correct-type-of-bgw_notify_pid.patch (text/plain) patch v2-0001
- v2-0002-Standardize-format-for-printing-PIDs.patch (text/plain) patch v2-0002
- v2-0003-Remove-pgpid_t-type-use-pid_t-instead.patch (text/plain) patch v2-0003
On 04.10.22 10:15, Peter Eisentraut wrote: > I wanted to propose the attached patch to get rid of the custom pgpid_t > typedef in pg_ctl. Since we liberally use pid_t elsewhere, this seemed > plausible. > > However, this patch fails the CompilerWarnings job on Cirrus, because > apparently under mingw, pid_t is "volatile long long int", so all the > printf placeholders mismatch. However, we print pid_t as %d in a lot of > other places, so I'm confused why this fails here. I figured out that in most places we actually store PIDs in int, and in the cases where we use pid_t, casts before printing are indeed used and necessary. So nevermind that. In any case, I took this opportunity to standardize the printing of PIDs as %d. There were a few stragglers. And then the original patch to get rid of pgpid_t in pg_ctl, now updated with the correct casts for printing. I confirmed that this now passes the CompilerWarnings job.
Commits
-
Remove pgpid_t type, use pid_t instead
- 5035c93c8a5a 16.0 landed
-
Standardize format for printing PIDs
- 1b11561cc1de 16.0 landed
-
doc: Correct type of bgw_notify_pid
- 34df7b9dfdee 16.0 landed