RE: [HACKERS] Client Connection redirection support for PostgreSQL - Mailing list pgsql-hackers

From Satyanarayana Narlapuram
Subject RE: [HACKERS] Client Connection redirection support for PostgreSQL
Date
Msg-id MWHPR21MB08293E49A3060302567CA21991DA0@MWHPR21MB0829.namprd21.prod.outlook.com
Whole thread Raw
In response to Re: [HACKERS] Client Connection redirection support for PostgreSQL  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Client Connection redirection support for PostgreSQL  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
Please see the attached patch with the comments.

Changes in the patch:
    A client-side PGREDIRECTLIMIT parameter has been introduced to control the maximum number of retries. 
    BE_v3.1 sends a ProtocolNegotiation message. FE_v3.1 downgrades to v3.0 upon receipt of this message.
    FE falls back to v3.0 if 3.1 is not supported by the server.


    >> I hadn't really thought deeply about whether redirection should happen before or after authentication.  For the
mostpart, before seems better, because it seems a bit silly to force people to authenticate just so that you can tell
themto go someplace else.  Also, that would lead to double authentication,          which might for example result in
multiplepassword prompts, which users might either dislike or find confusing.  
 

    Yes, redirection before authentication would avoid multiple password prompts.

Thanks,
Satya

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: JIT compiling with LLVM v11
Next
From: Pavel Stehule
Date:
Subject: Re: pg_get_functiondef forgets about most GUC_LIST_INPUT GUCs