Request a Demo
Home   >   mailing lists

Re: Replace current implementations in crypt() and gen_salt() to OpenSSL - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Replace current implementations in crypt() and gen_salt() to OpenSSL
Date
Msg-id 202501201200.k2wamndxyxr5@alvherre.pgsql
Whole thread Raw
In response to Replace current implementations in crypt() and gen_salt() to OpenSSL  ("Koshi Shibagaki (Fujitsu)" <shibagaki.koshi@fujitsu.com>)
List pgsql-hackers
Tree view 
On 2025-Jan-15, Daniel Gustafsson wrote:

> > On 14 Jan 2025, at 13:12, Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote:

> > Also: I'm not sure whether we should bump the version of pgcrypto.
> > It should be done when the API is changed, but the patch does not
> > do. Thought?
> 
> I don't think this constitutes a change which warrants a version bump
> so I've left that out for now.

Extension versions need to be changed only when the SQL definition of
the module is modified.  If the patch does not require a .sql script
that would run with ALTER EXTENSION UPDATE, then you should not modify
the extension version.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
<Schwern> It does it in a really, really complicated way
<crab> why does it need to be complicated?
<Schwern> Because it's MakeMaker.

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Psql meta-command conninfo+
Next
From: Amit Kapila
Date:
Subject: Re: create subscription with (origin = none, copy_data = on)