Excerpts from Dimitri Fontaine's message of vie mar 23 16:51:57 -0300 2012: > > Alvaro Herrera <alvhe...@commandprompt.com> writes: > >> Yes, for pg_depend, no I don't know how to make that work with pointing > >> to the extensions directly, because the whole point here is to be able > >> to depend on a feature rather than the whole extension. > > > > Yes, I understand that -- but would it work to have the feature > > resolution be done at install/upgrade time, and once it's resolved, you > > record it by storing the extension than contains the feature? That way > > I don't think so, because at upgrade time you then typically only have > the new .control file with the new set of features, and you need to > act on the difference between the old and new features compared to the > current other packages dependencies towards them.
Aha, right. So you still need an index on (oid), one on (extoid), and one on (extfeature). -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
