Thread: initdb problems handling super username with spaces.

initdb problems handling super username with spaces.

From
"Francisco Figueiredo Jr."
Date:
Hi all,
I just get postgresql from cvs and could compile perfectly on cygwin!!
Great work guys!!!

But when I run the initdb script, it fails with the following message:


The database cluster will be initialized with locale C.

Fixing permissions on existing directory /var/pgsqlcvs/... ok
creating directory /var/pgsqlcvs//base... ok
creating directory /var/pgsqlcvs//global... ok
creating directory /var/pgsqlcvs//pg_xlog... ok
creating directory /var/pgsqlcvs//pg_clog... ok
creating template1 database in /var/pgsqlcvs//base/1... ok
creating configuration files... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ok
setting privileges on built-in objects... ERROR:  user "Francisco" does 
not exis
t
IN:  get_usesysid (lsyscache.c:1737)

initdb failed.


I'm running with an account name "Francisco Figueiredo"

I know this can't be a major issue, but I just wanted let you know.
I could easily workaround by passing a "non-spaced" name as the super 
user with the -U option.

psql also seems to be with problems as it says it can't find PQFreemem 
in the pq.dll

But I could use the psql from the 7.3.2 release :)

Again, great work guys!

-- 
Regards,

Francisco Figueiredo Jr.

------
"My grandfather once told me that there are two
kinds of people: those
who work and those who take the credit. He told me
to try to be in the
first group; there was less competition there."
- Indira Gandhi



Re: initdb problems handling super username with spaces.

From
Tom Lane
Date:
"Francisco Figueiredo Jr." <fxjrlists@yahoo.com.br> writes:
> [ initdb fails with superuser name that contains spaces ]

I've put in some fixes for the most obvious problems, though I'd not
want to swear there are no other places that are careless about this.

> psql also seems to be with problems as it says it can't find PQFreemem 
> in the pq.dll

Sounds like a version-compatibility problem.  Sure you've got the right DLL?
        regards, tom lane