Re: pgsql: Add pg_alterckey utility to change the cluster key

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add pg_alterckey utility to change the cluster key
Date: 2020-12-28 02:43:23
Message-ID: 20201228024323.GA1697@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sun, Dec 27, 2020 at 12:44:50PM -0500, Bruce Momjian wrote:
> > Based on the number of concerns raised by various people over the last
> > couple of days (including myself, one point being the refactoring of
> > the ciphers taken from pgcrypto that should have been in its own
> > commit), I agree that it would be better to revert this code for now.
>
> OK, I will do so in the next few hours. My followup will be to:
>
> * register it for the commit-fest so it gets cfbot and other visibility
> * modify pgcrypto to use the new AES API (the SHA512 call no longer exists)
> * develop TAP tests, though as I mentioned, they will be odd

Patch set reverted. This was obviously a bad idea. I also apologize to
anyone who was disturbed on Christmas by my activity.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com

The usefulness of a cup is in its emptiness, Bruce Lee

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2020-12-28 09:47:38 Re: pgsql: Fix memory leak in plpgsql's CALL processing.
Previous Message Bruce Momjian 2020-12-28 02:37:55 pgsql: Revert "Add key management system" (978f869b99) & later commits

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2020-12-28 04:24:35 Re: Cache relation sizes?
Previous Message Tom Lane 2020-12-27 23:54:19 Re: Rethinking plpgsql's assignment implementation