Awesome, thank you!
That is exactly what I needed.
Didn't know it was that simple... duh!
On Aug 10, 2006, at 14:36, Thomas Pundt wrote:
On Thursday 10 August 2006 07:12, David Leangen wrote:
| > ALTER USER foo with encrypted password 'bar';
| > CREATE USER foo;
| > CREATE DATABASE bar owne
On Thursday 10 August 2006 07:12, David Leangen wrote:
| > ALTER USER foo with encrypted password 'bar';
| > CREATE USER foo;
| > CREATE DATABASE bar owner foo;
|
| That makes perfect sense, but how can I do this from the shell? Is
| there an easy way to wrap these so I can send them to postgres fr
David Leangen <[EMAIL PROTECTED]> 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 programmat
Thank you! Reply below.
On Aug 10, 2006, at 13:59, Joshua D. Drake wrote:
David Leangen wrote:
Hello!
I am trying to build an RPM package that will put my Postgres
installation into a known (usable) state, without requiring any
interaction.
To this effect, I need to do the following:
1.
Thank you. Reply below.
On Aug 10, 2006, at 13:54, Tom Lane wrote:
David Leangen <[EMAIL PROTECTED]> writes:
I am trying to build an RPM package that will put my Postgres
installation into a known (usable) state, without requiring any
interaction.
To this effect, I need to do the following
David Leangen wrote:
Hello!
I am trying to build an RPM package that will put my Postgres
installation into a known (usable) state, without requiring any
interaction.
To this effect, I need to do the following:
1. set password for superuser
2. createuser user
3. createdb -O user dbname
N
David Leangen <[EMAIL PROTECTED]> writes:
> I am trying to build an RPM package that will put my Postgres
> installation into a known (usable) state, without requiring any
> interaction.
> To this effect, I need to do the following:
> 1. set password for superuser
Basically, you can't. The
