From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Fabien COELHO <fabien(dot)coelho(at)ensmp(dot)fr> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_advisor schema proof of concept |
Date: | 2004-03-27 10:46:29 |
Message-ID: | 40655B85.30805@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fabien COELHO wrote:
>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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-03-27 17:04:49 | Re: A student research project on triggers |
Previous Message | Sean Chittenden | 2004-03-27 06:17:48 | Re: Per database users/admins, handy for database virtual hosting... |