Thanks for your response. It's not clear to me what more information you want; you seem to be following what I did pretty well.
On rereading, I notice an additional ambiguity. I believe I read "postgres account with which this package should perform administrative actions." as meaning the sql account *named* postgres (or, more generally, the overall sql admin account, which defaults to be postgres), which has overall admin rights for all postgres databases. Partly this is because the setup clearly needs to start from there in order to create the bacula user! I now suspect the intended meaning is the account this package will use, i.e., bacula. There is also some ambiguity in whether account refers to a database account (so postgres is an adjective describing the account type) or a linux account, though in context it seemed to me all references were to database accounts. So I think I was attempting to navigate the responses when I had set a password for bacula but not postgres, and interpreting various questions as referring to one or the other. I interpreted the first question as being about the bacula sql account (password) and the second as being about the postgres sql account (no password). My hope is that the setup questions not lead to a dead end, or the revelation in question #2 of information necessary to answer question #1 properly. And I also hope the installer can cope with this split situation of a password for one account (bacula) but not the other (postgres). I know I did eventually get it all working. Some bacula-specific context may be relevant: there needs to be remote access to the bacula database since clients may be on different machines. Since ident is insecure on a network, that means the bacula database should have a password, as well as the necessary configuration to permit remote access using passwords. So this hybrid situation (ident only for posgres db user and no password; password for bacula) seems likely to arise in practice. I assume your references to "indent" were meant as "ident". I'm pretty sure postgres allows multiple authentication mechanisms so one could access accounts on the local machine using ident and access the same accounts remotely using a password. The configuration includes restrictions on which hosts and can use which mechanisms. My concern about multiple names was mostly that either the installer or postgres itself would get confused about whether access was local or remote if postgres is installed with a system name of, e.g., pg.me.org and bacula is installed with a name of bac.me.org, but those are aliases for the same machine. Ross
