On 10/15/2017 10:54, Karl Denninger wrote:
On 10/15/2017 10:47, Tom Lane wrote:
Karl Denninger <karl@denninger.net> writes:
Attempting to migrate to 10.0 from 9.6, which has had "tsearch2" loaded
for backward compatibility since "forever" (which I suspect is no longer
really required as the capability is internal and has been for a long
time) results in this blowup logged in loadable_libraries.txt:
could not load library "$libdir/tsearch2": ERROR: could not access file
"$libdir/tsearch2": No such file or directory
So what's causing this to be requested on startup and how do I kill it?
Look for '$libdir/tsearch2' in the pg_proc.probin column of each
DB in the installation ...
regards, tom lane
Thanks... found it.
--
New problem -- davical appears to rely on something that got changed to disallowed....
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 (SEL
ECT 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] F
ROM group_member WHERE member_id = $1) AS expanded
Oct 15 11:07:08 NewFS postgres[92560]: [5-8] WHERE exp
anded.g_id IS NOT NULL;
Oct 15 11:07:08 NewFS postgres[92560]: [5-9]
Oct 15 11:07:08 NewFS postgres[92560]: [5-10] 2017-10-15 11:07:08.473 CDT [92560
] CONTEXT: SQL function "expand_memberships" during startup
That's a killer until the Davical people work on their code....