On Thu, 15 Aug 2002, Tom Lane wrote:
> Vince Vielhaber <vev@michvhf.com> writes:
> > But it doesn't need to affect anyone, even if it's enabled. Isn't
> > the lack of an @ just as good as an @ at the end of the username?
>
> No, because there isn't any @ in the incoming connection request in the
> normal-user case: just a user name and a database name, which *we* have
> to assemble into user@database.
>
> We can't really expect the users to do this for us (give user@database
> as their full user name). There are a number of reasons why I don't
> wanna do that, but the real showstopper is that the username field of
> the connection request packet is only 32 bytes wide, and we cannot
> enlarge it without a protocol breakage. Fitting "user@database" in 32
> bytes would be awfully restrictive about your user and database names.
Ok, I misunderstood. I thought it was the user going to have to type
that in based on some of yesterday's comments.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 56K Nationwide Dialup from $16.00/mo
atPop4 Networking http://www.camping-usa.com http://www.cloudninegifts.com http://www.meanstreamradio.com
http://www.unknown-artists.com
==========================================================================
