Tom Raney wrote: > >> RELOPTINFO (tenk1): rows=10000 width=244 > >> path list: > >> SeqScan(tenk1) rows=10000 cost=0.00..434.00 > >> IdxScan(tenk1) rows=10000 cost=0.00..583.25 > >> pathkeys: ((tenk1.unique2, onek.unique2)) <--- > > > >> cheapest startup path: > >> SeqScan(tenk1) rows=10000 cost=0.00..434.00 > > > >> cheapest total path: > >> SeqScan(tenk1) rows=10000 cost=0.00..434.00 > > > > Hm, I don't recognize this output format, is it coming from some custom > > code? > > Yes, it is. I thought it was easier to read the OPTIMIZER_DEBUG > output with the relation names instead of the relation indexes. I > will post a patch against CVS HEAD if you think it will help others.
Personally I would like to see optimizer debug become a configuration parameter rather than a compile-time parameter. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
