Thread: debug flag

Hi,

If I want to compile the PostgreSQL 6.2.1 code with the -g flag, which Makefile
should I add it. I would like to run it thru a debugger. I am compiling it
with gcc; so I should be able to use xgdb, right?

The sort cost in the planner is assumed to be 0. So, there is an unfair bias
towards sort-merge join in the optimizer. If I want to add a sort cost, will
it be enough to add it in the make_sortplan() function in
optimizer/plan/planner.c.
Is the size of the relation to be sorted estimated at that time?
If not what is the best way to do this?

Thanks
--shiby

>
> Hi,
>
> If I want to compile the PostgreSQL 6.2.1 code with the -g flag, which Makefile
> should I add it. I would like to run it thru a debugger. I am compiling it
> with gcc; so I should be able to use xgdb, right?
>
> The sort cost in the planner is assumed to be 0. So, there is an unfair bias
> towards sort-merge join in the optimizer. If I want to add a sort cost, will
> it be enough to add it in the make_sortplan() function in
> optimizer/plan/planner.c.
> Is the size of the relation to be sorted estimated at that time?
> If not what is the best way to do this?

I think this is fixed in 6.3.  Beta is Feb 1.

--
Bruce Momjian
maillist@candle.pha.pa.us

On Mon, 19 Jan 1998, Shiby Thomas wrote:

> Hi,
>
> If I want to compile the PostgreSQL 6.2.1 code with the -g flag, which Makefile
> should I add it. I would like to run it thru a debugger. I am compiling it
> with gcc; so I should be able to use xgdb, right?

    From Makefile.global:

##############################################################################
# COPT
#
# COPT is for options that the sophisticated builder might want to vary
# from one build to the next, like options to build Postgres with
debugging
# information included.  COPT is meant to be set on the make command line,
# for example with the command "make COPT=-g".  The value you see set here
# is the default that gets used if the builder does not give a value for
# COPT on his make command.
#
#