Re: pg_advisor schema proof of concept - Mailing list pgsql-hackers

From Andreas Pflug
Subject Re: pg_advisor schema proof of concept
Date
Msg-id 40697529.8080201@pse-consulting.de
Whole thread Raw
In response to Re: pg_advisor schema proof of concept  (Fabien COELHO <coelho@cri.ensmp.fr>)
List 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






pgsql-hackers by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: pg_dump end comment
Next
From: Fabien COELHO
Date:
Subject: with vs without oids in pg_catalog.*