<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
All,<br>
<br>
I ran into an issue installing Evergreen today. It turned out to be
an issue with a feature merged onto the main branch. The breaking
code:<br>
<br>
....<br>
CREATE OR REPLACE FUNCTION evergreen.redact_value(<br>
input_data anycompatible,<br>
skip_redaction BOOLEAN DEFAULT FALSE,<br>
redact_with anycompatible DEFAULT NULL<br>
) RETURNS anycompatible AS $f$<br>
....<br>
<br>
The error that is generated:<br>
<br>
psql:reporter-schema.sql:579: ERROR: type anycompatible does not
exist<br>
<br>
I brought it up on <a
href="http://irc.evergreen-ils.org/evergreen/2024-09-20#i_561373">IRC</a><br>
<br>
"anycompatible" doesn't appear to be supported until Postgres 13.<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.postgresql.org/docs/13/datatype-pseudo.html">https://www.postgresql.org/docs/13/datatype-pseudo.html</a><br>
<br>
Just throwing the issue out there to the larger group.<br>
<br>
I'm all for removing PG[10,11,12] support starting with Evergreen
3.14. But there might be a way to continue to support the older
versions with some tweaks to our install process and/or SQL code.<br>
<br>
<pre class="moz-signature" cols="72">--
-Blake-
Conducting Magic
Will consume any data format
MOBIUS</pre>
</body>
</html>