I was reading the section about Planner Method Configuration, and I just don't
get why all the options have this message: "This is used for debugging the
query planner". Are they all debugging options, because they don't look like.

http://www.postgresql.org/docs/current/interactive/
-> runtime-config.html#RUNTIME-CONFIG-QUERY

--
15:45:02 up 64 days, 22:01, 2 users, load average: 1.49, 1.32, 0.85
-----------------------------------------------------------------
Martín Marqués | select 'mmarques' || '@' || 'unl.edu.ar'
Centro de Telematica | DBA, Programador, Administrador
Universidad Nacional
del Litoral
-----------------------------------------------------------------


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Martin Marques <martin@bugs.unl.edu.ar> writes:[color=blue]
> I was reading the section about Planner Method Configuration, and I just don't
> get why all the options have this message: "This is used for debugging the
> query planner". Are they all debugging options, because they don't look like.[/color]

The enable_xxx options are debugging options in the sense that they're
not meant to be used in routine operations. They are intended to make
it possible to experiment with alternative plan choices --- but ideally
you should be able to get the planner to pick a good plan choice of its
own accord. You may need to tweak the cost parameters to reflect your
platform more accurately, or you may need to tune some other settings,
or gather more complete data statistics. If none of this helps it's
grounds for a bug report.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings