The database is not crashing thankfully. We are waiting for the errors to
come back to turn up logging in the hopes of creating the reproducible set.
Mike Broers writes:
> I will do my best to provide a reproducible test case. Is there any more
> information I can supply in the meantime that would help?
Well ... just to clarify, are you suffering any crashes in your database?
Because really the "fixing incomplete split" code shouldn't get ent
I will do my best to provide a reproducible test case. Is there any more
information I can supply in the meantime that would help?
Mike Broers writes:
> We have an ltree column (tree_path) that has a gist index
> (index_nodes_on_tree_path). This is in a 9.3.5 database. Recently errors
> started occurring in the postgres log on some updates to this table:
> fixing incomplete split in index "index_nodes_on_tree_path", block
Hello,
We have an ltree column (tree_path) that has a gist index
(index_nodes_on_tree_path). This is in a 9.3.5 database. Recently errors
started occurring in the postgres log on some updates to this table:
fixing incomplete split in index "index_nodes_on_tree_path", block 2358
STATEMENT: UPD
