Does anyone ever use OPTIMIZER_DEBUG?

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Does anyone ever use OPTIMIZER_DEBUG?
Date: 2023-09-28 21:20:39
Message-ID: CAApHDvoCdjo8Cu2zEZF4-AxWG-90S+pYXAnoDDa9J3xH-OrczQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

In c4a1933b4 I pushed a fix for a 4 year old bug in print_path() where
I'd forgotten to add handling for TidRangePaths while working on
bb437f995.

4 years is quite a long time for such a bug. Maybe that's because
nobody uses OPTIMIZER_DEBUG. I certainly don't, and Tom mentions [1]
he doesn't either.

Is there anyone out there who uses it?

If not, it's about 320 lines of uselessness.

David

[1] https://www.postgresql.org/message-id/951421.1695911023@sss.pgh.pa.us

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2023-09-28 21:50:32 Re: On login trigger: take three
Previous Message David Steele 2023-09-28 21:14:22 The danger of deleting backup_label