| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: TRACE_SORT defined by default |
| Date: | 2019-04-25 20:54:58 |
| Message-ID: | CAH2-Wzm4HB1PtOfhPbFAv-qOm5H332urMpqDMq7PaV4TKN=qPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 25, 2019 at 1:52 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> But the proposal is not to remove the _code_. The proposal is just to
> remove that "#ifdef" lines that would make it conditionally compilable,
> *if* the symbol that they test weren't always enabled. In other words,
> turn it from "always compiled, but you can turn it off although nobody
> does" into "always compiled".
Tom suggested that we might want to remove the code as an alternative.
We have two almost-opposite proposals here.
As I said, I think that the way that we think about or define
developer options frames this discussion.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-25 20:56:33 | Re: TRACE_SORT defined by default |
| Previous Message | Alvaro Herrera | 2019-04-25 20:52:03 | Re: TRACE_SORT defined by default |