I've created a recommender based off a table I have in the RecDB. My understanding is that when I run a recommending query after creating a recommender, RecDB automatically sees a created recommender and uses it for a faster response.
However, after creating a recommender and running a recommend query, I get the following error server side
select * from relations recommend anime_id to user_id on score using ItemCosCF where user_id = 499231 order by score desc limit 20;
LOG: server process (PID 17044) was terminated by signal 11: Segmentation fault
DETAIL: Failed process was running: select * from relations recommend anime_id to user_id on score using ItemCosCF where user_id = 499231 order by score desc limit 20;
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
FATAL: the database system is in recovery mode
LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2016-04-28 03:13:29 UTC
LOG: database system was not properly shut down; automatic recovery in progress
LOG: record with zero length at C/2257FB40
LOG: redo is not required
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
Could anyone kindly suggest what the problem might be? Thanks for your time.
This is on the database we were discussing earlier. Any thoughts @Sarwat? We will be happy to provide you with the necessary DB files to replicate this error.
Hi,
I've created a recommender based off a table I have in the RecDB. My understanding is that when I run a recommending query after creating a recommender, RecDB automatically sees a created recommender and uses it for a faster response.
However, after creating a recommender and running a recommend query, I get the following error server side
Could anyone kindly suggest what the problem might be? Thanks for your time.