aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/variable.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2022-10-14 08:37:12 +0200
committerPeter Eisentraut <peter@eisentraut.org>2022-10-14 08:38:53 +0200
commit1b11561cc1de7596f6f7cb750743af94b9d168f7 (patch)
treea16c63b0dfd1d35a520337f5342f8cf59c0ffd1e /src/backend/commands/variable.c
parent34df7b9dfdeee442cf43060b6499bedc5f619f7f (diff)
downloadpostgresql-1b11561cc1de7596f6f7cb750743af94b9d168f7.tar.gz
postgresql-1b11561cc1de7596f6f7cb750743af94b9d168f7.zip
Standardize format for printing PIDs
Most code prints PIDs as %d, but some code tried to print them as long or unsigned long. While this is in theory allowed, the fact that PIDs fit into int is deeply baked into all PostgreSQL code, so these random deviations don't accomplish anything except confusion. Note that we still need casts from pid_t to int, because on 64-bit MinGW, pid_t is long long int. (But per above, actually supporting that range in PostgreSQL code would be major surgery and probably not useful.) Discussion: https://www.postgresql.org/message-id/289c2e45-c7d9-5ce4-7eff-a9e2a33e1580@enterprisedb.com
Diffstat (limited to 'src/backend/commands/variable.c')
0 files changed, 0 insertions, 0 deletions