| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Mark Hill <Mark(dot)Hill(at)sas(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, Phil Rau <Phil(dot)Rau(at)sas(dot)com>, Michael King <Michael(dot)King(at)sas(dot)com>, Ashley Stephens <Ashley(dot)Stephens(at)sas(dot)com> |
| Subject: | Re: Error Creating pgcrypto Extension |
| Date: | 2026-09-18 09:43:38 |
| Message-ID: | BE670ABC-CF65-4811-9E23-61031609D160@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 18 Sep 2026, at 02:05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> On the whole, seeing that installing pgcrypto into pg_catalog has
> not worked since v13 and there's been hardly any complaints about
> that, I'm not sure that we should risk breaking working setups to
> allow it.
I wouldn't be opposed to removing gen_random_uuid from pgcrypto, it's a hack
and documented as obsolete in all supported versions. Supporting installing
pgcrypto in pg_catalog would not be a motivator though, trimming unnecessary
code from pgcrypto is however appealing
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Rau | 2026-09-18 14:33:33 | RE: Error Creating pgcrypto Extension |
| Previous Message | Tom Lane | 2026-09-18 00:05:02 | Re: Error Creating pgcrypto Extension |