"Couldn't parse plan": hint clueless users that swap fields

[Krysztophe]

If a user swaps the Plan and Query fields (ie: he puts EXPLAIN SELECT 1 ; in Plan, and QUERY PLAN .... and so on in Query, which is after all the most intuitive way when copy-pasting both query and plan in a hurry), the result is simply « Couldn't parse plan ».

To avoid to lose time to try reformatting a perfectly fine plan, it is possible to add a message like this in the error box ?

Did you put a SQL query in the Plan field?

This is not possible to detect all possible cases, but these are the most current symptoms:

• QUERY PLAN, (cost=, rows= width= are present in the Query field
• SELECT, EXPLAIN, UPDATE, INSERT, WITH is the 1st word of the Plan field
• =# or ; appear in the Plan field.

(Please don't ask why I came to this idea 🙄 )

[pgiraud]

Closing as won't fix.

The new "couln't parse" message showing the failing plan may help.