At some point I suggested to integrate SQLite debugging code/statements (EXPLAIN etc) and build FG by default with it included, but the people involved in that code basically disagreed that this would be needed back then:
Subject: Nasal bugfixes - for 2.12?
Hooray wrote:Maybe, there's some SQLite env variable that can be set to dump even more stuff at the SQLite layer ? Like I said, that's on a fairly powerful system and came as a surprise to me, because I didn't expect to see this on Linux at all. If other people can confirm this being the case for them, too I'd seriously consider disabling POI in 2.12 by default until this is solved, simply because it could be a major showstopper for people entirely new to FG, if they have to wait between 5-10 minutes for FG to start up, while looking totally unresponsive ...
As previously mentioned elsewhere, I think we need to look into using SQLite profiling and/or "EXPLAIN QUERY PLAN" to get to the bottom of this, because this has been affecting a number of users/platforms during the last release cycles. Is there a single place where I can patch SQL statements to have the "EXPLAIN QUERY PLAN" prefix and register callbacks for profiling ?