I debugged index with gdb and found that it is segmentation fault in my procedure named
gist_mov_consistent it is only 7 lines. So I think it is worth to publish it to public,
Datum gist_mov_consistent(PG_FUNCTION_ARGS){ GISTENTRY *entry = (GISTENTRY *)PG_GETARG_POINTER(0); BOX *query = PG_GETARG_BOX_P(1); StrategyNumber strategy = (StrategyNumber)PG_GETARG_UINT16(2); if (DatumGetMovP(entry->key) == NULL || query == NULL) PG_RETURN_BOOL(FALSE); PG_RETURN_BOOL(obj_contains(DatumGetMovP(entry->key), query));}Do you have any ideas where is the problem ? :)
Best regards,
Sergej Galkin
On Wed, Jan 13, 2010 at 8:42 PM, Sergej Galkin
<sergej.galkin@gmail.com> wrote:
Hello all,
I am a student-magister and I'm writting my magister work. I realized gist index TPR tree - it is like a simple R tree but moving :)
Everything is compiling ok, I creating table and index, but after whese code - DB is restarting :(((
set enable_seqscan = false
select * from table_of_moving_objects where mov_obj ~ box '(0,0) (1,1)'
I can not understand why DB is restarting ? It is restarting when SQL begins use index :(((
Can anybody help me , I would by appretiate every people who downloads my sources, try to deploy index and maybe solve where is the problem.
Best regards,
Sergej Galkin
