What I am looking for is that our DB is doing X selects a min.
Turning on logging isn't an option as it will create too much IO in
On May 23, 2006, at 11:15 AM, Mischa Sandberg wrote:
> Dan Gorman wrote:
>> I might be completely crazy here, but it seems every other
>> database exposes select query stats. Postgres only exposes updates/
>> deletes/inserts. Is there something I am missing here?
> You can EXPLAIN ANALYZE a SELECT, just like i/u/d -- but then you
> don't get the normal result set back. Is that what you mean?
> You can turn on log_min_duration_statement and get total SELECT
> There's a thread in pgsql-hackers ("Re: Porting MSSQL to PGSQL:
> trace and profile") about server-side logging of query plans and
> stats (for all four of s/i/u/d), which is indeed not there in PG.
> Engineers think that equations approximate reality.
> Physicists think that reality approximates the equations.
> Mathematicians never make the connection.
> ---------------------------(end of
> TIP 3: Have you checked our extensive FAQ?
In response to
pgsql-performance by date
|Next:||From: Mischa Sandberg||Date: 2006-05-23 18:32:28|
|Subject: Re: Selects query stats?|
|Previous:||From: Dan Gorman||Date: 2006-05-23 17:40:01|
|Subject: Selects query stats?|