Re: configure datatype name > 31?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mark McEahern <marklists(at)mceahern(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: configure datatype name > 31?
Date: 2002-06-03 01:06:18
Message-ID: 200206030106.g5316Jp23632@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Tom Lane wrote:
> "Mark McEahern" <marklists(at)mceahern(dot)com> writes:
> > Tom, thanks for your reply. I am now able to create databases and users
> > with longer names, but I am unable to login with the long username.
>
> I think you're stuck on that, unless you want to be *really*
> incompatible with the rest of the world. The startup packet format has
> hard-wired field sizes --- see src/include/libpq/pqcomm.h:
>
> #define SM_DATABASE 64
> #define SM_USER 32
> #define SM_OPTIONS 64
> #define SM_UNUSED 64
> #define SM_TTY 64
>
> Don't ask me why SM_USER is different from the rest :-(
>
> If you change these I'd strongly advise bumping the protocol minor
> version number, so that you don't have weird behavior should you try
> to interoperate with standard code.
>
> This is another thing that should be on the list of stuff to fix when
> we next change the FE/BE protocol ...

Comment added to source that SM_USER length should match the others.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Bhuvan A 2002-06-03 08:30:24 Re: Mirroring ENTIRE DATABASE.
Previous Message Bruce Momjian 2002-06-02 20:22:08 Re: Authentication in batch processing