Specifically, this is blowing up:
Oct 15 11:07:08 NewFS postgres[92560]: [5-1] 2017-10-15 11:07:08.473 CDT
[92560]
ERROR: set-returning functions are not allowed in CASE at character 129
Oct 15 11:07:08 NewFS postgres[92560]: [5-2] 2017-10-15 11:07:08.473 CDT
[92560]
HINT: You might be able to move the set-returning function into a
LATERAL FROM
item.
Oct 15 11:07:08 NewFS postgres[92560]: [5-3] 2017-10-15 11:07:08.473 CDT
[92560]
QUERY:
Oct 15 11:07:08 NewFS postgres[92560]: [5-4] SELECT group_id FROM
group_mem
ber WHERE member_id = $1
Oct 15 11:07:08 NewFS postgres[92560]: [5-5] UNION
Oct 15 11:07:08 NewFS postgres[92560]: [5-6] SELECT expanded.g_id
FROM (SELECT CASE WHEN $2 > 0 THEN expand_memberships( group_id, $2 - 1)
END AS g_id
Oct 15 11:07:08 NewFS postgres[92560]:
[5-7] FROM group_member WHERE
member_id = $1) AS expanded
Oct 15 11:07:08 NewFS postgres[92560]: [5-8]
WHERE expanded.g_id IS NOT NULL;
Postgres 10 made this change and it appears the impacted queries have
not been updated in Davical as of yet....
--
Karl Denninger
karl@denninger.net <mailto:karl@denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
Oct 15 11:07:08 NewFS postgres[92560]: [5-1] 2017-10-15 11:07:08.473 CDT
[92560]
ERROR: set-returning functions are not allowed in CASE at character 129
Oct 15 11:07:08 NewFS postgres[92560]: [5-2] 2017-10-15 11:07:08.473 CDT
[92560]
HINT: You might be able to move the set-returning function into a
LATERAL FROM
item.
Oct 15 11:07:08 NewFS postgres[92560]: [5-3] 2017-10-15 11:07:08.473 CDT
[92560]
QUERY:
Oct 15 11:07:08 NewFS postgres[92560]: [5-4] SELECT group_id FROM
group_mem
ber WHERE member_id = $1
Oct 15 11:07:08 NewFS postgres[92560]: [5-5] UNION
Oct 15 11:07:08 NewFS postgres[92560]: [5-6] SELECT expanded.g_id
FROM (SELECT CASE WHEN $2 > 0 THEN expand_memberships( group_id, $2 - 1)
END AS g_id
Oct 15 11:07:08 NewFS postgres[92560]:
[5-7] FROM group_member WHERE
member_id = $1) AS expanded
Oct 15 11:07:08 NewFS postgres[92560]: [5-8]
WHERE expanded.g_id IS NOT NULL;
Postgres 10 made this change and it appears the impacted queries have
not been updated in Davical as of yet....
--
Karl Denninger
karl@denninger.net <mailto:karl@denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/