Re: Add "host" to startup packet

> On 2 Apr 2023, at 18:33, Tom Lane wrote: > > Greg Stark writes: >> My question is a bit different. How does this interact with TLS SNI. >> Can you just use the SNI name given in the TLS handshake? Should the >> server require them to match? Is there any value to having a separate >> source for

Re: Add "host" to startup packet

Greg Stark writes: > My question is a bit different. How does this interact with TLS SNI. > Can you just use the SNI name given in the TLS handshake? Should the > server require them to match? Is there any value to having a separate > source for this info? Is something similar available in GSSAPI

Re: Add "host" to startup packet

On Sun, 2 Apr 2023 at 11:38, Tom Lane wrote: > > Even if all that infrastructure sprang into existence, is this really any > more useful than basing your switching on the host's resolved IP address? > I'm doubtful that there's enough win there to justify pushing this rock > to the top of the mount

Re: Add "host" to startup packet

Lev Kokotov writes: > Patch attached below. TLDR, I'd like to add "host" to the startup packet. I don't think this is of any use at all in isolation. What is the server going to do with it? What's your plan for persuading clients other than libpq to supply it? How are poolers supposed to handl

Re: Add "host" to startup packet

Hi Lev,02.04.2023, 14:43, "Lev Kokotov" :Patch attached below. TLDR, I'd like to add "host" to the startup packet.I'm trying to run multiple Postgres servers in a multi-tenant environment behind a pooler. Currently, the only way to differentiate Postgres databases is with the user/dbname combinatio

Add "host" to startup packet

Hello, Patch attached below. TLDR, I'd like to add "host" to the startup packet. I'm trying to run multiple Postgres servers in a multi-tenant environment behind a pooler . Currently, the only way to differentiate Postgres databases is with the user/dbname com