| From: | Vladimir Churyukin <vladimir(at)churyukin(dot)com> |
|---|---|
| To: | pghackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Multiple startup messages over the same connection |
| Date: | 2024-01-22 19:58:36 |
| Message-ID: | CAFSGpE2RxR51HXezRwO+vJ4MPHORTTc3djEkJztGkWON4cWP0g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
A question about protocol design - would it be possible to extend the
protocol, so it can handle multiple startup / authentication messages over
a single connection? Are there any serious obstacles? (possible issues with
re-initialization of backends, I guess?)
If that is possible, it could improve one important edge case - where you
have to talk to multiple databases on a single host currently, you need to
open a separate connection to each of them. In some cases (multitenancy for
example), you may have thousands of databases on a host, which leads to
inefficient connection utilization on clients (on the db side too). A lot
of other RDBMSes don't have this limitation.
thank you,
-Vladimir Churyukin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tristan Partin | 2024-01-22 20:04:43 | Re: make dist using git archive |
| Previous Message | Christoph Berg | 2024-01-22 19:48:40 | Re: psql: Allow editing query results with \gedit |