Re: A costing analysis tool - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: A costing analysis tool
Date
Msg-id 43565957020000250000013A@gwmta.wicourts.gov
Whole thread Raw
In response to A costing analysis tool  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: A costing analysis tool
List pgsql-hackers
This would require capture of information beyond what I was thinking
about in terms of schema.  Do you think we need to capture just index
type, or something more?  Do you propose that we capture the pg_*
metadata related to every object referenced in the plan, every object
related to every table in the query, or everything in the entire
database?


>>> Josh Berkus <josh@agliodbs.com>  >>>

[smip]

the only way you're going analyze index costing by type 
of index is if the index name is stored somewhere (db_object) so that it

can be matched to its characteristics.

[snip]




pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: 'a' == 'a ' (Was: RE: [pgsql-advocacy] [GENERAL] Oracle buys Innobase)
Next
From: "Marc G. Fournier"
Date:
Subject: Re: [pgsql-advocacy] [GENERAL] Oracle buys Innobase