Re: [ADMIN] Cannot connect to the database (PG 7.3)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
Cc: Michiel Lange <michiel(at)minas(dot)demon(dot)nl>, pgsql-hackers(at)postgreSQL(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: [ADMIN] Cannot connect to the database (PG 7.3)
Date: 2003-01-29 02:00:52
Message-ID: 16720.1043805652@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

"Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> How about throwing an error if an all digit user name is given to create
> user as already alluded to?

I do *not* want to do that; that's creating a user-visible restriction
for the convenience of one very small part of the implementation. I
think this behavior is a bug, and we should fix it not institutionalize
the misbehavior. Just haven't figured out how, yet.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2003-01-29 04:40:58 Re: [ADMIN] Cannot connect to the database (PG 7.3)
Previous Message Nigel J. Andrews 2003-01-29 01:44:55 Re: [ADMIN] Cannot connect to the database (PG 7.3)

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2003-01-29 02:02:05 Re: Request for qualified column names
Previous Message Tom Lane 2003-01-29 01:50:58 Testing for int64 (was Re: [COMMITTERS] pgsql-server/ /configure /configure.in...)