Re: Index AM API cleanup

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Alex Wang <alex(dot)wang(at)enterprisedb(dot)com>
Subject: Re: Index AM API cleanup
Date: 2024-08-21 20:16:50
Message-ID: 9e54431a-c61b-47f1-bac3-71b60b203179@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2024-08-21 We 4:09 PM, Mark Dilger wrote:
>
>> On Aug 21, 2024, at 12:34 PM, Kirill Reshke<reshkekirill(at)gmail(dot)com> wrote:
>>
>> Hi! Why is the patch attached as .tar.bz2? Usually raw patches are sent here...
> I worried the patch set, being greater than 1 MB, might bounce or be held up in moderation.

Yes, it would have required moderation AIUI. It is not at all
unprecedented to send a compressed tar of patches, and is explicitly
provided for by the cfbot: see
<https://wiki.postgresql.org/wiki/Cfbot#Which_attachments_are_considered_to_be_patches.3F>

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-08-21 20:47:11 Re: Better error message when --single is not the first arg to postgres executable
Previous Message Mark Dilger 2024-08-21 20:09:52 Re: Index AM API cleanup