Ok.
A more precise question is: on the client side, whether PHP or anything else, can you take advantage of the information available and provide some usable somehow "dedicated" interface that would make it easy to access the available informations? What would help for that purpose?
The current proposal is that the advices would be tables in a schema, so just by browsing the tables one can access advices. However, the tables contain the advice data, but explanations about what these advices mean are in another table.
So maybe there is an interface job that would be welcome to show both the
explanations and the data of interest for these explanations? Just like
in psql "\*" shortcuts query about pg_tables to show informations.
No problem, as long as referencing data is contained in the advice tables (i.e. referencing the 'offending' object), not just text so the advice can be shown as attribute of each object.
Regards, Andreas
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
