Re: BUG #6513: explain (analyze, buffers) and toasted fields

Поиск
Список
Период
Сортировка
От Marti Raudsepp
Тема Re: BUG #6513: explain (analyze, buffers) and toasted fields
Дата
Msg-id CABRT9RCAUObsWMG9KBhmeaKgvjC22QA+OA8aNOv-kXRLHzO13g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #6513: explain (analyze, buffers) and toasted fields  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
On Mon, Mar 12, 2012 at 17:23, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> EXPLAIN ANALYZE *necessarily* does less work than the real query,
> because it doesn't transmit the results to the client (which is going
> to be a dominant cost in a lot of situations). =C2=A0I'm not sure whether
> running the I/O functions would provide a useful improvement in
> verisimilitude or not

Granted, but I can see how one would expect the detoasting to be
accounted for in EXPLAIN, since it's something that's usually done
*inside* the database (as opposed to network overhead). That would
give a more accurate picture of where the time is being spent.

Now, another question is whether to use text or binary output
functions. And where to account the time, since this happens outside
of the plan tree.

At the very least, I think this gotcha should be documented on the EXPLAIN =
page.

Regards,
Marti

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

Предыдущее
От: Jaime Casanova
Дата:
Сообщение: Re: BUG #6517: Volatile function erroneously optimized, does not consider change in schema path
Следующее
От: Sergey Burladyan
Дата:
Сообщение: Re: BUG #6480: NLS text width problem