Re: Request for comment on setting binary format output per session

Поиск
Список
Период
Сортировка
От Jelte Fennema
Тема Re: Request for comment on setting binary format output per session
Дата
Msg-id CAGECzQR_S=gQ8SQHNaMzEiASp6cpFnxxaTDpTY6pGB=7P+3Vtg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Request for comment on setting binary format output per session  (Dave Cramer <davecramer@gmail.com>)
Ответы Re: Request for comment on setting binary format output per session  (Dave Cramer <davecramer@gmail.com>)
Список pgsql-hackers
On Mon, 9 Oct 2023 at 21:08, Dave Cramer <davecramer@gmail.com> wrote:
> So if we use <schema>.<type> would it be possible to have something like <builtin> which represents a set of well
knowntypes?
 
> My goal here is to reduce the overhead of naming all the types the client  wants in binary. The list of well known
typesis pretty long.
 
> Additionally we could have a shorthand for removing a well known type.

You're only setting this once in the lifetime of the connection right,
i.e. right at the start (although pgbouncer could set it once per
transaction in the worst case). It seems like it shouldn't really
matter much to optimize the size of the "SET format_binary=..."
command, I'd expect it to be at most 1 kilobyte. I'm not super opposed
to having a shorthand for some of the most commonly wanted built-in
types, but then we'd need to decide on what those are, which would add
even more discussion/bikeshedding to this thread. I'm not sure the win
in size is worth that effort.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: CHECK Constraint Deferrable
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Remove distprep