| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Vince Vielhaber <vev(at)michvhf(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Open 7.3 items |
| Date: | 2002-08-14 22:56:26 |
| Message-ID: | 17169.1029365786@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> How about if we just document that they have to create a
> postgres(at)template1 user before flipping the switch. That way, there is
> no special user, no PG_INSTALLER file, and no double-tests for user
> names.
... and no useful superuser account; if you can't connect to anything
except template1 then you ain't much of a superuser.
To get around that you'd have to create postgres(at)db1, postgres(at)db2,
postgres(at)db3, etc etc. This would be a huge pain in the neck; I think
it'd render the scheme impractical. (Keep in mind that anybody who'd be
interested in this feature at all has probably got quite a number of
databases to contend with.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2002-08-14 22:56:56 | Re: journaling in contrib ... |
| Previous Message | Tom Lane | 2002-08-14 22:52:17 | Re: pg_dump output portability |