Re: constants for tar header offsets - Mailing list pgsql-hackers

From Tom Lane
Subject Re: constants for tar header offsets
Date
Msg-id 2661235.1681833969@sss.pgh.pa.us
Whole thread Raw
In response to Re: constants for tar header offsets  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: constants for tar header offsets  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Apr 18, 2023 at 11:38 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 2. The header size is defined as 512 bytes, but this doesn't sum to 512:
>> +       TAR_OFFSET_PREFIX = 345         /* 155 byte string */

> I think that what happened is that whoever designed the original tar
> format decided on 512 byte blocks. And the header did not take up the
> whole block. The USTAR format is an extension of the original format
> which uses more of the block, but still not all of it.

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?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: constants for tar header offsets
Next
From: Nikita Malakhov
Date:
Subject: Re: [PATCH] Compression dictionaries for JSONB