I think the code is currently used only by the Query Plan Guidance (QPG) component. If we execute ANALYZE for it, performance would drop. I guess we could have separate public methods, one for QPG and one that we use in the provider class.

I see, looking over the PostgresProvider class, I can only see that the PostgresExplainGenerator is being used in getQueryPlan method which it will definitely drop the performance by adding the analyze part, but you also mentioned I should create another method for the provider class, could you maybe elaborate on that part?

We could add an enum (see

@yaojiejia, I see you have been working on multiple other PRs. Do you think it would be possible to focus on the open ones, so we can merge those first?

@yaojiejia, I see you have been working on multiple other PRs. Do you think it would be possible to focus on the open ones, so we can merge those first?

Of course, will prioritize these for now, thanks

We could add an enum (see

sqlancer/src/sqlancer/postgres/PostgresProvider.java

Line 129 in 49c7358

CREATE_VIEW(PostgresViewGenerator::create);

). In this enum, we can specify a newly-created method in the explain generator that can generate the full range of EXPLAIN, while we can keep using the restricted method for QPG.

Just included a method for EXPLAIN. Lmk if this is something we are looking for