Re: Fix for pg_upgrade user flag - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Fix for pg_upgrade user flag
Date
Msg-id 201105072248.p47Mmni09724@momjian.us
Whole thread Raw
In response to Re: Fix for pg_upgrade user flag  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Fix for pg_upgrade user flag  (Andrew Dunstan <andrew@dunslane.net>)
List 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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Fix for pg_upgrade user flag
Next
From: Andrew Dunstan
Date:
Subject: Re: Fix for pg_upgrade user flag