pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedlog_min_cost_statement
4+ messages / 4 participants
[nested] [flat]
* log_min_cost_statement
@ 2004-04-13 15:26 Nichlas Löfdahl <crotalus@acc.umu.se>
2004-04-13 18:26 ` Re: log_min_cost_statement Bruce Momjian <pgman@candle.pha.pa.us>
2004-04-13 18:45 ` Re: log_min_cost_statement Tom Lane <tgl@sss.pgh.pa.us>
2004-04-13 18:46 ` Re: log_min_cost_statement Peter Eisentraut <peter_e@gmx.net>
0 siblings, 3 replies; 4+ messages in thread
From: Nichlas Löfdahl @ 2004-04-13 15:26 UTC (permalink / raw)
To: pgsql-admin
Hello!
Would it be possible to have an option "log_min_cost_statement", similar to
"log_min_duration_statement" except that it logs all statement that has
an minimum cost estimated by the planner? I think it would be easier to
find unoptimized queries that way.
Just a thought!
/Nichlas
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: log_min_cost_statement
2004-04-13 15:26 log_min_cost_statement Nichlas Löfdahl <crotalus@acc.umu.se>
@ 2004-04-13 18:26 ` Bruce Momjian <pgman@candle.pha.pa.us>
2 siblings, 0 replies; 4+ messages in thread
From: Bruce Momjian @ 2004-04-13 18:26 UTC (permalink / raw)
To: Nichlas Löfdahl <crotalus@acc.umu.se>; +Cc: pgsql-admin
Nichlas Löfdahl wrote:
> Hello!
>
> Would it be possible to have an option "log_min_cost_statement", similar to
> "log_min_duration_statement" except that it logs all statement that has
> an minimum cost estimated by the planner? I think it would be easier to
> find unoptimized queries that way.
Uh, yea, I guess we could, but the costs are more comparison with other
costs, not really with other queries, I think, so I am not sure it would
be meaningful.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: log_min_cost_statement
2004-04-13 15:26 log_min_cost_statement Nichlas Löfdahl <crotalus@acc.umu.se>
@ 2004-04-13 18:45 ` Tom Lane <tgl@sss.pgh.pa.us>
2 siblings, 0 replies; 4+ messages in thread
From: Tom Lane @ 2004-04-13 18:45 UTC (permalink / raw)
To: Nichlas Löfdahl <crotalus@acc.umu.se>; +Cc: pgsql-admin
Nichlas =?iso-8859-1?Q?L=F6fdahl?= <crotalus@acc.umu.se> writes:
> Would it be possible to have an option "log_min_cost_statement", similar to
> "log_min_duration_statement" except that it logs all statement that has
> an minimum cost estimated by the planner? I think it would be easier to
> find unoptimized queries that way.
Why would you want to filter on the planner's cost estimate rather than
the true runtime?
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: log_min_cost_statement
2004-04-13 15:26 log_min_cost_statement Nichlas Löfdahl <crotalus@acc.umu.se>
@ 2004-04-13 18:46 ` Peter Eisentraut <peter_e@gmx.net>
2 siblings, 0 replies; 4+ messages in thread
From: Peter Eisentraut @ 2004-04-13 18:46 UTC (permalink / raw)
To: Nichlas Löfdahl <crotalus@acc.umu.se>; pgsql-admin
Nichlas Löfdahl wrote:
> Would it be possible to have an option "log_min_cost_statement",
> similar to "log_min_duration_statement" except that it logs all
> statement that has an minimum cost estimated by the planner? I think
> it would be easier to find unoptimized queries that way.
If you believe that the costs have any absolute meaning at all then they
should be proportional to the execution time, so the existing setting
should be enough.
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2004-04-13 18:46 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-04-13 15:26 log_min_cost_statement Nichlas Löfdahl <crotalus@acc.umu.se>
2004-04-13 18:26 ` Bruce Momjian <pgman@candle.pha.pa.us>
2004-04-13 18:45 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-04-13 18:46 ` Peter Eisentraut <peter_e@gmx.net>
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