| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Remove INT64_HEX_FORMAT and UINT64_HEX_FORMAT |
| Date: | 2025-08-02 09:09:16 |
| Message-ID: | 0ac47b5d-e5ab-4cac-98a7-bdee0e2831e4@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
These were introduced (commit efdc7d74753) at the same time as we were
moving to using the standard inttypes.h format macros (commit
a0ed19e0a9e). It doesn't seem useful to keep a new already-deprecated
interface like this with only a few users, so remove the new symbols
again and have the callers use PRIx64.
(Also, INT64_HEX_FORMAT was kind of a misnomer, since hex formats all
use unsigned types.)
[should be backpatched to PG18]
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Remove-INT64_HEX_FORMAT-and-UINT64_HEX_FORMAT.patch | text/plain | 4.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-08-02 09:47:42 | Bug in pg_dump --filter? - Invalid object types can be misinterpreted as valid |
| Previous Message | Alexander Lakhin | 2025-08-02 08:00:00 | Re: Improving tracking/processing of buildfarm test failures |