hey john, On Wed, 2007-04-25 at 08:43 -0500, John Goerzen wrote: > I think that the first problem the original submitter references here is > a dbconfig-common one, but I don't know if it's possible to have a > solution. > > If indeed Debian's postgresql packages are configured for the admin user > to use ident auth by default, and if the postgres user is authorized but > root is not by default, then we have no way to configure things by > default anyway. Perhaps that is a PostgreSQL bug, but I wonder if there > is some way that dbconfig-common could make clear what is going on?
from my understanding, the default postgres install allows
authentication via "ident sameuser" for local access, and "password"
based access for connections to localhost via tcp/ip. if this is the
case, things ought to work with the right configuration selections.
for database setup, dbconfig-common should automatically be smart enough
to su to the postgres user to create the schemas/users/etc.
for the rest, it may depend on user input to debconf for the right
connection settings. it may be that the host stuff is only prompted if
they select the advanced/remote option, my memory for the config logic
is a little dusty.
regardless, if it doesn't work out of the box i'd say there's room for
improvement, since that's sort of the whole idea behind
dbconfig-common :) i'm open to suggestions if this is the case.
sean
signature.asc
Description: This is a digitally signed message part
