| From: | Dave Cramer <davecramer(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
| Subject: | Re: Request for comment on setting binary format output per session |
| Date: | 2023-03-22 12:18:25 |
| Message-ID: | CADK3HHK5mkci80CYmVnR4dMPfKRhuAjx-ny2xx7F9GqjTwFwBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
If I recall the protocol-extension design correctly, such a setting
could only be set at session start, which could be annoying --- at the
very least we'd have to tolerate entries for unrecognized data types,
since clients couldn't be expected to have checked the list against
the current server in advance.
The protocol extension design has the drawback that it can only be set at
startup.
What if we were to allow changes to the setting after startup if the client
passed the cancel key as a unique identifier that only the driver would
know?
Dave Cramer
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2023-03-22 12:18:31 | Re: Avoid use deprecated Windows Memory API |
| Previous Message | Dave Cramer | 2023-03-22 12:14:57 | Re: Request for comment on setting binary format output per session |