Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: Josh berkus <josh(at)agliodbs(dot)com>, Tomasz Ostrowski <tometzky+pg(at)ato(dot)waw(dot)pl>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all
Date: 2016-06-08 03:04:05
Message-ID: 26771.1465355045@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> 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.

Yeah, my guess is that the OP's example where analyzing just one column
was significantly cheaper boiled down to some of the other columns being
mostly toasted data. Otherwise it's hard to see how there's much more
expense in analyzing them all.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Tripp 2016-06-08 04:09:47 Re: BUG #14150: Attempted to delete invisible tuple
Previous Message Michael Paquier 2016-06-08 02:59:10 Re: BUG #14178: output of jsonb_object and json_object doesn't match textually

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-06-08 03:07:30 Re: Reviewing freeze map code
Previous Message Robert Haas 2016-06-08 03:01:07 Re: Rename max_parallel_degree?