debug_sortsupport GUC?

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: pgsql-hackers(at)postgresql(dot)org
Subject: debug_sortsupport GUC?
Date: 2015-03-22 03:28:01
Message-ID: 87d241en4r.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The text abbreviation code has a compile-time option to emit DEBUGn
elogs. I made no attempt to add these to the numeric abbreviation code
because I find such things completely unhelpful; when you need to
investigate such things other than in initial development, it's unlikely
that you will be in a position to recompile. Also, as I showed at some
length earlier, even recompiling with an apparently irrelevant change
can have enough of an effect on performance to make investigation more
complex.

So if these debugging elogs are to be kept at all, I propose that rather
than being compile-time options they should be controlled by a
debug_sortsupport GUC. Opinions?

--
Andrew (irc:RhodiumToad)

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2015-03-22 04:00:40 Re: NUMERIC private methods?
Previous Message Peter Eisentraut 2015-03-22 02:55:23 Re: [PATCH] Add transforms feature