| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Review of: explain / allow collecting row counts without timing info |
| Date: | 2012-02-03 17:28:33 |
| Message-ID: | CA+TgmoYv545Tmibp2gm9P6SCx4md+6fr8bs8MAaW6pBf6R4htw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 3, 2012 at 12:08 PM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
> I don't think changing the EXPLAIN syntax this way is a good idea. I think
> that one option should not silently enable/disable others, so ROWS should
> not enable ANALYZE automatically.
I didn't propose that. The point is that the desired behavior
(however we name it) is a SUBSET of what ANALYZE does.
So we can either:
1. Have ANALYZE enable all the behavior, and have another option
(TIMING) that can be used to turn some of it back on again.
2. Have ANALYZE enable all the behavior, and have another option
(ROWS) that enables just the subset of it that we want.
I prefer #2 to #1, because I think it's a bit confusing to have an
option whose effect is to partially disable another option. YMMV, of
course.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2012-02-03 19:56:13 | Re: Review of: explain / allow collecting row counts without timing info |
| Previous Message | Tomas Vondra | 2012-02-03 17:08:22 | Re: Review of: explain / allow collecting row counts without timing info |