On Mon, Sep 26, 2005 at 11:03:33AM +0200, Andreas Tille wrote: > >what should be entered into pg_hba.conf. that way dbconfig-common > >could, in its debconf prompt, tell the admin what needed to be added, > >giving the admin a chance to do it himself/herself if preferred. > > What about the conf.d idea brouth up in the thread > > PostgreSQL access rights handling > > of the dbconfig-common mailing list? honestly, i'm happy enough with the method suggested by martin, because it makes such an issue a moot point. that is, postgres could later decide to move to such a method, or change the configuration method entirely, and then dbconfig-common will not need to be changed to reflect this. if the tools ship in postgres packages maintained by martin, he'd be able to update the tools when the method is updated. additionally, i think that it would be fairly clean wrt to policy this way, as we are not directly modifying the config file, but instead doing so via the method provided by the package maintainer (we should still ask though). that said, i still think that the conf.d approach has some merit to it, but with all my other commitments i really don't have the time and motivation to start a discussion thread (which would doubtlessly include a defense of the suggestion) with the postgres developers about it. sean --
Attachment:
signature.asc
Description: Digital signature