From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Leangen <postgres(at)leangen(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Programmatically changing passwords |
Date: | 2006-08-10 05:36:17 |
Message-ID: | 11476.1155188177@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
David Leangen <postgres(at)leangen(dot)net> writes:
> Yes, that is my point. After having installed the standard postgresql
> package, I would then install my custom-postgres-config package. In
> this package, I tinker with the default configuration so I can put
> postgres into a known state programmatically, without any user
> interaction.
> The problem is that createuser doesn't allow for this: it prompts the
> user for a password, which does not work in this situation, as you
> pointed out.
I rather doubt that: the default RPM installation uses ident
authentication. Which has got plenty of downsides, but unexpected
password prompts is not one of them. Perhaps you are making your
configuration changes in a bad order?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Pundt | 2006-08-10 05:36:36 | Re: Programmatically changing passwords |
Previous Message | David Leangen | 2006-08-10 05:12:22 | Re: Programmatically changing passwords |