| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | 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 22:48:49 |
| Message-ID: | 201105072248.p47Mmni09724@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> On l?r, 2011-05-07 at 13:50 -0400, Bruce Momjian wrote:
> > I was really wondering if I should be using that hard-coded name,
> > rather than allowing the user to supply it. They have to compile in a
> > different name, and I assume that name is accessible somewhere.
>
> "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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-05-07 23:03:16 | Re: Fix for pg_upgrade user flag |
| Previous Message | Bruce Momjian | 2011-05-07 22:46:29 | Re: Fix for pg_upgrade user flag |