| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)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-30 13:24:57 |
| Message-ID: | 40697529.8080201@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Fabien,
Fabien COELHO wrote:
>Hello Andreas,
>
>
>
>>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.
>>
>>
>
>What do you mean by 'referencing data'?
>Things like oid attributes referencing pg_class or pg_constraint or
>pg_index?
>
>
in a way. If you're advising about e.g. a table, the row should
reference that table by oid. This way, admin tools can LEFT JOIN the
advisory table to display that data.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-03-30 14:13:10 | Re: pg_dump end comment |
| Previous Message | Fabien COELHO | 2004-03-30 13:16:01 | with vs without oids in pg_catalog.* |