Re: pgcrypto: Remove internal padding implementation

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Jacob Champion <pchampion(at)vmware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgcrypto: Remove internal padding implementation
Date: 2022-03-22 08:01:09
Message-ID: 74a55fd7-077a-74f7-a2c3-e41e4d401e3d@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22.03.22 00:51, Nathan Bossart wrote:
> On Wed, Mar 16, 2022 at 11:12:06AM +0100, Peter Eisentraut wrote:
>> Right, the previous behaviors were clearly faulty. I have updated the
>> commit message to call out the behavior change more clearly.
>>
>> This patch is now complete from my perspective.
>
> I took a look at this patch and found nothing of concern.

committed

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-03-22 08:09:16 Re: logical decoding and replication of sequences
Previous Message Masahiko Sawada 2022-03-22 07:48:53 Re: Add index scan progress to pg_stat_progress_vacuum