Re: Does anyone ever use OPTIMIZER_DEBUG? - Mailing list pgsql-hackers

From David Rowley
Subject Re: Does anyone ever use OPTIMIZER_DEBUG?
Date
Msg-id CAApHDvpzRrmzA2nv0N_ehMD1ajDQto+EpjLzfWoOW=qVu6eRRw@mail.gmail.com
Whole thread Raw
In response to Re: Does anyone ever use OPTIMIZER_DEBUG?  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Does anyone ever use OPTIMIZER_DEBUG?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 3 Oct 2023 at 12:29, David Rowley <dgrowleyml@gmail.com> wrote:
>
> On Fri, 29 Sept 2023 at 10:59, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > We could also discuss keeping the "tracing" aspect of it, but
> > replacing debug_print_rel with pprint(rel), which'd still allow
> > removal of all the "DEBUG SUPPORT" stuff at the bottom of allpaths.c.
> > That's pretty much all of the maintenance-requiring stuff in it.
>
> To assist discussion, I've attached a patch for that.

It looks like nobody is objecting to this.  I understand that not
everyone who might object will have read this email thread, so what I
propose to do here is move along and just commit the patch to swap out
debug_print_rel and use pprint instead.  If that's done now then there
are around 10 months where we could realistically revert this again if
someone were to come forward with an objection.

Sound ok?

David



pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Re: [PoC/RFC] Multiple passwords, interval expirations
Next
From: Tom Lane
Date:
Subject: Re: Does anyone ever use OPTIMIZER_DEBUG?