On Mon, Apr 19, 2010 at 7:18 PM, Tom Lane <[email protected]> wrote: > Alvaro Herrera <[email protected]> writes: >> Robert Haas escribió: >>> Would it be possible to set up a skeleton environment where we can >>> access shared catalogs only and then decide on which database we're >>> using later? > >> Eh? We already do that ... In fact the autovac launcher is always >> connected to shared catalogs, without being connected to any one >> database in particular (cf. get_database_list) > > Hmm. The AV launcher is only permitted to touch pg_database. > At the time there were considerable advantages to that restriction, > but subsequent changes (like getting rid of the need for manual > maintenance of pg_attribute entries for bootstrap catalogs) might > mean that it wouldn't be too painful to extend this capability to > pg_authid etc. Could be worth thinking about.
Perhaps we should add a TODO. ...Robert -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
