> >> Were you able to create a user `www-data'?
> >I believe that the createuser script did it for me.
> Yes, it does. Very inconsistent!
> >> I agree that there is a bug, but it is that the error message is
> >> wrong!
> >If grant would permit the username to be quoted in ' characters, then
> >the problem ought to go away, I think.
>
> Currently, it appears that the authors don't want to change, so it is
> necessary to specify a postgres user-id when connecting.
"Don't want to change"? Probably not. We're trying to figure out how to
cope with an ever-increasing number of interested users _and_
developers, and don't always react quickly to good suggestions.
The topic just came up recently, as I recall, and your suggestions are
good. Do you really want the patch applied which disables the more
general user names, or do you want to move more slowly and try to get
full user names in v6.4 (we have several months to get this right; in
fact we may already have them; see below :)
> However there is, as you say in another mail, no convenient way of
> doing that automatically. We need an environment variable or a
> command-line option to specify the user and (optionally) password.
Sorry, I didn't follow the whole discussion. Is the problem only with
explicit CREATE USER and GRANT commands in SQL, or are there other
interfaces which would show problems too (you mention command-line
options above, but I don't know to what).
Oh, I just tried something:
tgl=> create user "hi-there";
CREATE USER
tgl=> select usename from pg_user;
usename
--------
postgres
tgl
hi-there
(3 rows)
Isn't this what you want?? I haven't figured out how to get GRANT to
work, but it seems to swallow the double-quoted user name as it
should...
- Tom
btw, how is it going with the docs conversion, Oliver? I'd expect that
it would keep you out of trouble for a little while at least :)
