Skip site navigation (1) Skip section navigation (2)

Re: compile error with -DOPTIMIZER_DEBUG

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Jan Urbański <wulczer(at)wulczer(dot)org>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: compile error with -DOPTIMIZER_DEBUG
Date: 2009-11-29 14:35:34
Message-ID: 14074.1259505334@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> You know, the last couple of times I've touched that code, I've been
>> wondering why we bother to maintain it.  Personally I always use pprint()
>> when I'm interested in a printout of a plan tree.  Is anyone actually
>> using the printout code in allpaths.c?

> I thought OPTIMIZER_DEBUG showed us all the possible paths, not just the
> final plan.

Yeah, but we could repoint that code at pprint.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-11-29 14:47:17
Subject: Re: cvs chapters in our docs
Previous:From: Gokulakannan SomasundaramDate: 2009-11-29 14:22:38
Subject: A small issue in CommentCast function

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group