Re: Finer Extension dependencies - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Finer Extension dependencies
Date
Msg-id m2ty1f5b5e.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Finer Extension dependencies  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> So you still need an index on (oid), one on (extoid), and one on
> (extfeature).

Yes. And the main use case for the index on (extoid) is listing a given
extension's features, that we want to order by their name, then the set
of indexes I've been defining is now:

Indexes:   "pg_extension_feature_name_index" UNIQUE, btree (extfeature)   "pg_extension_feature_oid_index" UNIQUE,
btree(oid)   "pg_extension_feature_extoid_name_index" btree (extoid, extfeature)
 

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Finer Extension dependencies
Next
From: Tom Lane
Date:
Subject: Re: Refactoring simplify_function (was: Caching constant stable expressions)