From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Jim C. Nasby <decibel@decibel.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tuning planner cost estimates
Date: Thu, 19 May 2005 13:16:21 -0400
Message-ID: <5514.1116522981@sss.pgh.pa.us> (raw)
In-Reply-To: <200505190931.47662.josh@agliodbs.com>
References: <20050518002236.GU30902@decibel.org>
<200505190931.47662.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> I think a first step would be, in fact, to develop a tool that allows us to
> put EXPLAIN ANALYZE results in a database table. Without that, there is no
> possibility of statistical-scale analysis.
AFAIK you can do that today using, eg, plpgsql:
for rec in explain analyze ... loop
insert into table values(rec."QUERY PLAN");
end loop;
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, decibel@decibel.org
Subject: Re: Tuning planner cost estimates
In-Reply-To: <5514.1116522981@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox