From: | Fabien COELHO <fabien(dot)coelho(at)ensmp(dot)fr> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_advisor schema proof of concept |
Date: | 2004-03-25 16:15:06 |
Message-ID: | Pine.LNX.4.58.0403251703460.7217@sablons.cri.ensmp.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
> Both phpPgAdmin (me) and the pgAdmin team have added or have thought
> about adding some 'schema analysis' features to our products. If
> pg_advisor is available, I certainly won't bother and I will just
> recommend to people that they install it.
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.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-03-25 16:19:09 | Re: pg_advisor schema proof of concept |
Previous Message | Tom Lane | 2004-03-25 15:29:28 | Re: < operator for user-defined types |