Re: Request for comment on setting binary format output per session
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dave Cramer <davecramer@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>,
Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-03-26T22:12:26Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Silence compiler warning introduced in 1edb3b491b
- fba2112b1569 17.0 cited
Dave Cramer <davecramer@gmail.com> writes: > Well I was presuming that they would just pass the parameter on. If they > didn't then binary_format won't work with them. In the case that they do > pass it on, then DISCARD_ALL will reset it and future borrows of the > connection will have no way to set it again; effectively making this a one > time setting. I would not expect DISCARD ALL to reset a session-level property. regards, tom lane