| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fix for pg_upgrade user flag |
| Date: | 2011-05-07 23:03:16 |
| Message-ID: | 4DC5CFB4.9080800@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/07/2011 06:48 PM, Bruce Momjian wrote:
>> "postgres" is not compiled in. It's whatever user you run initdb under.
>> In particular, in the regression tests, it is probably not "postgres".
> Thanks. I get confused because the 'postgres' database is hardcoded in,
> but not the username. Not sure why I am so easily confused.
There is a requirement for a known database name, but no requirement for
a known superuser name.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-05-08 00:19:28 | Re: pg_upgrade's bindir options could be optional |
| Previous Message | Bruce Momjian | 2011-05-07 22:48:49 | Re: Fix for pg_upgrade user flag |