[PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG - Mailing list pgsql-hackers

From Ankit Kumar Pandey
Subject [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
Date
Msg-id 1fd8e494-4740-4108-6d06-d5a173836047@gmail.com
Whole thread Raw
Responses Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Hi all,


This is patch for TODO item: Improve ability to display optimizer analysis using OPTIMIZER_DEBUG

As per as suggestion in the mailing list which is to replace current mechanism of getting optimizer log via OPTIMIZER_DEBUG macro

to something more configurable (which doesn't require rebuilding postgres from source code). This patch replaces OPTIMIZER_DEBUG

by introducing a GUC show_optimizer_log which can be configured on and off to display (or hide) previously generated log from stdout to postmaster's log.

Please check attached patch, any feedback is appreciated.

-- 
Regards,
Ankit Kumar Pandey
Attachment

pgsql-hackers by date:

Previous
From: Ankit Kumar Pandey
Date:
Subject: Todo: Teach planner to evaluate multiple windows in the optimal order
Next
From: Tom Lane
Date:
Subject: Re: Error-safe user functions