Re: WIP: explain analyze with 'rows' but not timing
| От | Pavel Stehule |
|---|---|
| Тема | Re: WIP: explain analyze with 'rows' but not timing |
| Дата | |
| Msg-id | CAFj8pRCede2zQZ77sYr+ohf=ib4Lf004erFVhQD-OndKfYn-sA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: WIP: explain analyze with 'rows' but not timing (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: WIP: explain analyze with 'rows' but not timing
Re: WIP: explain analyze with 'rows' but not timing |
| Список | pgsql-hackers |
2011/12/23 Tom Lane <tgl@sss.pgh.pa.us>: > Tomas Vondra <tv@fuzzy.cz> writes: >> The motivation for this patch was that collection timing data often >> causes performance issues and in some cases it's not needed. But is this >> true for row counts? > > Perhaps more to the point, is there a use case for collecting timing > data without row counts? I find it hard to visualize a valid reason. yes - a searching of bad prediction Regards Pavel > > regards, tom lane > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: