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

Поиск
Список
Период
Сортировка
От Dave Cramer
Тема Re: Request for comment on setting binary format output per session
Дата
Msg-id CADK3HH+v50kAjTF9b2rCWzEu1ixWk31Mo-4VSR4T8RKe3GrhcQ@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  (Merlin Moncure <mmoncure@gmail.com>)
Список pgsql-hackers
Дерево обсуждения
> participating clients to receive GUC configured format.  I do not
> think that libpq's result format being able to be overridden by GUC
> is a good idea at all, the library has to to participate, and I
> think can be made to so so without adjusting the interface (say, by
> resultFormat = 3).

Interesting idea. I suppose you'd need to specify 3 for all result
columns? That is a protocol change, but wouldn't "break" older clients.
The newer clients would need to make sure that they're connecting to
v16+, so using the protocol version alone wouldn't be enough. Hmm.


So this only works with extended protocol and not simple queries. 
Again, as Peter mentioned it's already easy enough to confuse psql using binary cursors so 
it makes sense to fix psql either way.

If you use resultFormat (3) I think you'd still end up doing the Describe (which we are trying to avoid) to make sure you could receive all the columns in binary.

Dave 

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Minimal logical decoding on standbys
Следующее
От: Melanie Plageman
Дата:
Сообщение: Re: Should vacuum process config file reload more often