Re: GUC_REPORT for protocol tunables was: Re: Optimize binary serialization format of arrays with fixed size elements

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: GUC_REPORT for protocol tunables was: Re: Optimize binary serialization format of arrays with fixed size elements
Дата
Msg-id 778.1327335652@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: GUC_REPORT for protocol tunables was: Re: Optimize binary serialization format of arrays with fixed size elements  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: GUC_REPORT for protocol tunables was: Re: Optimize binary serialization format of arrays with fixed size elements  (Marko Kreen <markokr@gmail.com>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jan 23, 2012 at 9:59 AM, Marko Kreen <markokr@gmail.com> wrote:
>> Now that I think about it, same applies to bytea_output?

> Probably so.  But I think we need not introduce quite so many new
> threads on this patch.  This is, I think, at least thread #4, and
> that's making the discussion hard to follow.

Well, this is independent of the proposed patch, so I think a separate
thread is okay.  The question is "shouldn't bytea_output be marked
GUC_REPORT"?  I think that probably it should be, though I wonder
whether we're not too late.  Clients relying on it to be transmitted are
not going to work with existing 9.0 or 9.1 releases; so maybe changing
it to be reported going forward would just make things worse.
        regards, tom lane


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

Предыдущее
От: Dimitri Fontaine
Дата:
Сообщение: Re: Inline Extension
Следующее
От: Marko Kreen
Дата:
Сообщение: Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility