| From: | Josh berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomasz Ostrowski <tometzky+pg(at)ato(dot)waw(dot)pl> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all |
| Date: | 2016-06-06 20:23:30 |
| Message-ID: | 5755DBC2.9040007@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
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.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ap | 2016-06-07 01:42:34 | BUG #14178: output of jsonb_object and json_object doesn't match textually |
| Previous Message | Tom Lane | 2016-06-06 19:59:37 | Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-06-06 20:27:28 | Re: Reviewing freeze map code |
| Previous Message | Stephen Frost | 2016-06-06 20:18:19 | Re: Reviewing freeze map code |