Re: Order by (for 15 rows) adds 30 seconds to query time
От
Kevin Grittner
Тема
Re: Order by (for 15 rows) adds 30 seconds to query
time
Дата
Msg-id
4B16A46E020000250002CFC6@gw.wicourts.gov
Ответ на
Re: Order by (for 15 rows) adds 30 seconds to query time (Richard Neill)
Список
Дерево обсуждения
Order by (for 15 rows) adds 30 seconds to query time Richard Neill <rn214@cam.ac.uk>
Re: Order by (for 15 rows) adds 30 seconds to query time Jean-Michel Pouré <jmpoure@free.fr>
Re: Order by (for 15 rows) adds 30 seconds to query time Richard Neill <rn214@cam.ac.uk>
Re: Order by (for 15 rows) adds 30 seconds to query
time "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Order by (for 15 rows) adds 30 seconds to query time Richard Neill <rn214@cam.ac.uk>
Re: Order by (for 15 rows) adds 30 seconds to query time Matthew Wakeling <matthew@flymine.org>
Re: Order by (for 15 rows) adds 30 seconds to query time Craig Ringer <craig@postnewspapers.com.au>
Re: Order by (for 15 rows) adds 30 seconds to query
time "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Order by (for 15 rows) adds 30 seconds to query time Tom Lane <tgl@sss.pgh.pa.us>
Re: Order by (for 15 rows) adds 30 seconds to query
time "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Order by (for 15 rows) adds 30 seconds to query time Tom Lane <tgl@sss.pgh.pa.us>
Re: Order by (for 15 rows) adds 30 seconds to query
time "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Order by (for 15 rows) adds 30 seconds to query time Richard Neill <rn214@cam.ac.uk>
Re: Order by (for 15 rows) adds 30 seconds to query
time "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Order by (for 15 rows) adds 30 seconds to query time Richard Neill <rn214@cam.ac.uk>
Re: Order by (for 15 rows) adds 30 seconds to query
time "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Richard Neill wrote: > Regarding pg_statistic, I don't understand how to find the > relevant rows - what am I looking for? (the pg_statistic table is > 247M in size). I think the only relevant rows would be the ones with starelid = pg_class.oid for a table used in the query, and I think you could further limit it to rows where staattnum = pg_attribute.attnum for a column referenced in the WHERE clause or a JOIN's ON clause (including in the views). To help match them up, and to cover all the bases, listing the related pg_class and pg_attribute rows would help. Hopefully that will allow us to generate the same plan in an EXPLAIN, and then see how it gets such an overblown estimate of the result rows. -Kevin
В списке pgsql-performance по дате отправления
От: Richard Neill
Дата: