Re: listening addresses

From: "John Hansen" <john(at)geeknet(dot)com(dot)au>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: listening addresses
Date: 2004-03-15 20:48:33
Message-ID: 5066E5A966339E42AA04BA10BA706AE56161@rodrick.geeknet.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Idiot is such a strong word, don't you think?

-----Original Message-----
From: pgsql-hackers-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Andrew Dunstan
Sent: Tuesday, March 16, 2004 7:26 AM
To: Postgresql Hackers
Subject: Re: [HACKERS] listening addresses

I wrote:

> Josh Berkus wrote:
>
>> If I had time, I would also love to see setting the password for the
>> postgres user become part of the initdb script. However, I can see
>> that this wouldn't work with packages.
>>
>>
>>
>
> Orthogonal problem.
>

BTW, initdb is no longer a script - some idiot rewrote it in C :-)

And it does have a switch for setting the superuser password:

-W
--pwprompt

Makes initdb prompt for a password to give the database superuser.
If you don't plan on using password authentication, this is not
important. Otherwise you won't be able to use password
authentication until you have a password set up.

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if
your
joining column's datatypes do not match

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-03-15 20:54:38 Re: listening addresses
Previous Message Matthew T. O'Connor 2004-03-15 20:40:42 Re: rapid degradation after postmaster restart