Re: constants for tar header offsets
Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
From: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org"
<pgsql-hackers@postgresql.org>
Date: 2023-04-18T16:56:43Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > On Tue, Apr 18, 2023 at 12:06 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Hmm, you're right: I checked the POSIX.1-2018 spec as well, and >> it agrees that the prefix field is 155 bytes long. Perhaps just >> add another comment line indicating that 12 bytes remain unassigned? > > OK. Here's v2, with that change and a few others. It still has magic numbers for the sizes of the fields, should those also be named constants? - ilmari
Commits
-
Add and use symbolic constants for tar header offsets and file types.
- 6050b6a92d1e 17.0 landed