Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
Дата
Msg-id 21240.1207029996@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Ответы Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Список pgsql-jdbc
"Guillaume Smet" <guillaume.smet@gmail.com> writes:
> Another question is how we can be sure it doesn't happen again. The
> easiest way to test this is probably to have a JDBC test testing this
> exact feature in the future benchfarm. Any comment?

Yeah, the lack of any formal testing of the extended-Query protocol
is a real problem.  I'm not sure of a good fix, but it bears some
thinking about.  Not only do we not have an automated way to notice
if we broke functionality, but we don't really notice for either
extended or basic protocol if we hurt performance.

            regards, tom lane

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

Предыдущее
От: "Guillaume Smet"
Дата:
Сообщение: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
Следующее
От: "Guillaume Smet"
Дата:
Сообщение: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work