| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Request for comment on setting binary format output per session |
| Date: | 2023-10-10 14:35:28 |
| Message-ID: | CA+TgmoZyAh+hdN8zvHeN40n9vTstw8K1KjuWdgDuAMMbFAZqHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 10, 2023 at 10:30 AM Dave Cramer <davecramer(at)gmail(dot)com> wrote:
> Correct me if I am wrong, but the client has to request this. So I'm not sure how we would be surprised ?
Consider an application, a connection pooler, and a stored procedure
or function on the server. If this is controlled by a GUC, any of them
could set it at any point in the session. That could lead to the
application and/or the connection pooler being out of step with the
server behavior.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-10-10 14:50:55 | Re: On login trigger: take three |
| Previous Message | Robert Haas | 2023-10-10 14:33:50 | Re: Request for comment on setting binary format output per session |