| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, David Fetter <david(at)fetter(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New EXPLAIN option: ALL |
| Date: | 2019-05-21 16:32:21 |
| Message-ID: | CA+TgmoYxzEp1ejykNHJ95t1nJ8q63yPDeboi74GRzXceaJGMUw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 15, 2019 at 1:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> That seems too confusing.
>
> > Ok. Are you voting for using EXEC as a keyword to replace ANALYZE?
>
> FWIW, given the conflict against "EXPLAIN EXECUTE prepared_stmt_name",
> we should probably just drop the whole idea. It seemed like a great
> idea at the time, but it's going to confuse people not just Bison.
+1. I think trying to replace ANALYZE with something else is setting
ourselves up for years, possibly decades, worth of confusion. And
without any real benefit.
Defaulting BUFFERS to ON is probably a reasonable change, thuogh.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-05-21 16:34:40 | Re: A few more opportunities to use TupleTableSlotOps fields |
| Previous Message | Andres Freund | 2019-05-21 16:19:37 | Re: Minimal logical decoding on standbys |