| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Johannes Meidert <johannes(dot)meidert(at)rohde-schwarz(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5699: Postgres runs only under default user. |
| Date: | 2010-10-11 01:23:56 |
| Message-ID: | 4CB2672C.4000002@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 10/08/2010 07:53 PM, Johannes Meidert wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5699
> Logged by: Johannes Meidert
> Email address: johannes(dot)meidert(at)rohde-schwarz(dot)com
> PostgreSQL version: 9.0.1
> Operating system: windows
> Description: Postgres runs only under default user.
> Details:
>
> If a --superaccount is specified during installation other than 'postgres',
> the service will not start correctly and there are lots of errors "role
> <postgres> does not exist" in the DB error log.
> The option -- superaccount should be removed.
It does seem a bit odd - if the super account is wired into the database
cluster at initdb time, you'd think it'd be read from there on startup.
Comments, anybody? This report hasn't seen a response, but seems to have
some legitimacy as a usability issue if not an outright bug.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-11 03:25:44 | Re: BUG #5702: pg fails to use a conditional index even the where clause matches the condition |
| Previous Message | David Newall | 2010-10-10 22:42:30 | rollback to savepoint leads to transaction already in progress |