| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | <kevin(dot)kempter(at)dataintellect(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postgres password |
| Date: | 2006-06-16 10:14:43 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4013889DE@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
________________________________
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of DataIntellect
Sent: 15 June 2006 20:56
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] postgres password
You cannot use the postgres account without some tweaks, Sorry I
don't remember where I found this info - somewhere in the pgadmin
install docs.
If it does say that anywhere, I'd love to know where so I can remove it.
However this works:
Create a new superuser with a password, add connectivity to the
pg_hba.conf file if needed and pgadmin should work fine
The postgres account should be quite usable for this. You might need to
edit pg_hba.conf as well of course.
Regards,. Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Downs | 2006-06-16 10:40:59 | Re: minimizing downtime when upgrading |
| Previous Message | John Gunther | 2006-06-16 09:18:40 | Forcing backslash to be treated as ordinary string character |