Re: constants for tar header offsets

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tristan Partin <tristan(at)neon(dot)tech>
Cc: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: constants for tar header offsets
Date: 2023-08-01 17:57:02
Message-ID: CA+TgmoZNnd8ZbEH5xQH4feG4Y8mT7T05ine_QMFdMYRT7=pCug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 1, 2023 at 11:07 AM Tristan Partin <tristan(at)neon(dot)tech> wrote:
> A new API design would be great, but for right now v2 is good enough and
> should be committed. It is much easier to read the code with this patch
> applied.
>
> Marking as "Ready for Committer" since we all seem to agree that this is
> better than what exists.

Thanks, committed now.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2023-08-01 18:15:41 Re: Improve the performance of nested loop join in the case of partitioned inner table
Previous Message Robert Haas 2023-08-01 17:41:42 Re: pgsql: Fix search_path to a safe value during maintenance operations.