Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all
От | Jim Nasby |
---|---|
Тема | Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all |
Дата | |
Msg-id | 3d9303dc-f99c-b63c-73be-aa2214bebe73@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all (Josh berkus <josh@agliodbs.com>) |
Ответы |
Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all
|
Список | pgsql-hackers |
On 6/6/16 3:23 PM, Josh berkus wrote: > On 06/06/2016 01:38 PM, Tom Lane wrote: > >> Also, I'd be a bit inclined to disable the counter reset whenever a column >> list is specified, disregarding the corner case where a list is given but >> it includes all the table's analyzable columns. It doesn't really seem >> worth the effort to account for that case specially (especially after >> you consider that index expressions should count as analyzable columns). >> >> Thoughts? > > +1. Better to err on the side of duplicate analyzes than none at all. > > Also, I'm not surprised this took so long to discover; I doubt most > users are aware that you *can* analyze individual columns. Is there any significant advantage to not analyzing all columns? Only case I can think of is if you have a fair number of columns that have been toasted; otherwise I'd think IO would completely swamp any other considerations. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461
В списке pgsql-hackers по дате отправления: