pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedQuery Feromance
7+ messages / 3 participants
[nested] [flat]
* Query Feromance
@ 2006-03-20 14:59 Marco Furetto <furetto@bluestudio.it>
0 siblings, 1 reply; 7+ messages in thread
From: Marco Furetto @ 2006-03-20 14:59 UTC (permalink / raw)
To: pgsql-performance
Hello!
Can I Increment the perfomance of execution query?
Where is the instrument to analyze the query runnnig for create a Index
query for a single optimize that?
thank's
Marco "Furetto" Berri
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Query Feromance
@ 2006-03-20 16:34 Reimer <carlosreimer@terra.com.br>
parent: Marco Furetto <furetto@bluestudio.it>
0 siblings, 1 reply; 7+ messages in thread
From: Reimer @ 2006-03-20 16:34 UTC (permalink / raw)
To: pgsql-performance
Marco,
Could you give us the query you would like to improve performance?
----- Original Message -----
From: "Marco Furetto" <furetto@bluestudio.it>
To: <pgsql-performance@postgresql.org>
Sent: Monday, March 20, 2006 11:59 AM
Subject: [PERFORM] Query Feromance
> Hello!
>
> Can I Increment the perfomance of execution query?
>
> Where is the instrument to analyze the query runnnig for create a Index
> query for a single optimize that?
>
> thank's
>
> Marco "Furetto" Berri
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Query Feromance
@ 2006-03-21 08:25 Marco Furetto <furetto@bluestudio.it>
parent: Reimer <carlosreimer@terra.com.br>
0 siblings, 1 reply; 7+ messages in thread
From: Marco Furetto @ 2006-03-21 08:25 UTC (permalink / raw)
To: pgsql-performance
Hello!
I'm managing the db of a "Content Management environment" and I'm
searching for a "Query analyzer" to improve performance because i don't
know how many and what type of queries are executing on the system (for
the "where and join" block).
If i could have query's stats i could Optimize the queries indexes.
Thank's a lot!
Marco "Furetto" Berri
Reimer wrote:
> Marco,
>
> Could you give us the query you would like to improve performance?
>
>
> ----- Original Message ----- From: "Marco Furetto" <furetto@bluestudio.it>
> To: <pgsql-performance@postgresql.org>
> Sent: Monday, March 20, 2006 11:59 AM
> Subject: [PERFORM] Query Feromance
>
>
>> Hello!
>>
>> Can I Increment the perfomance of execution query?
>>
>> Where is the instrument to analyze the query runnnig for create a
>> Index query for a single optimize that?
>>
>> thank's
>>
>> Marco "Furetto" Berri
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 9: In versions below 8.0, the planner will ignore your desire to
>> choose an index scan if your joining column's datatypes do not
>> match
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Query Feromance
@ 2006-03-21 08:43 Thomas Pundt <mlists@rp-online.de>
parent: Marco Furetto <furetto@bluestudio.it>
0 siblings, 2 replies; 7+ messages in thread
From: Thomas Pundt @ 2006-03-21 08:43 UTC (permalink / raw)
To: pgsql-performance
Hi,
On Tuesday 21 March 2006 09:25, Marco Furetto wrote:
| I'm managing the db of a "Content Management environment" and I'm
| searching for a "Query analyzer" to improve performance because i don't
| know how many and what type of queries are executing on the system (for
| the "where and join" block).
as a first step, I'd enable query duration logging; in postgresql.conf
I have set
log_min_duration_statement = 3000
this will log each query that needs more than 3 seconds to complete.
The next step would be to "explain analyze" the problematic queries.
Ciao,
Thomas
--
Thomas Pundt <thomas.pundt@rp-online.de> ---- http://rp-online.de/ ----
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Query Feromance
@ 2006-03-21 09:56 Marco Furetto <furetto@bluestudio.it>
parent: Thomas Pundt <mlists@rp-online.de>
1 sibling, 1 reply; 7+ messages in thread
From: Marco Furetto @ 2006-03-21 09:56 UTC (permalink / raw)
To: pgsql-performance
ok, I enable query duration logging in postgresql.conf.
where is the instruments for analyze the statistics queries executing on
my db?
Eg.: Number of query executing, total time for executing a single query,
etc...
Thank's
Marco "Furetto" Berri
Thomas Pundt wrote:
> Hi,
>
> On Tuesday 21 March 2006 09:25, Marco Furetto wrote:
> | I'm managing the db of a "Content Management environment" and I'm
> | searching for a "Query analyzer" to improve performance because i don't
> | know how many and what type of queries are executing on the system (for
> | the "where and join" block).
>
> as a first step, I'd enable query duration logging; in postgresql.conf
> I have set
>
> log_min_duration_statement = 3000
>
> this will log each query that needs more than 3 seconds to complete.
>
> The next step would be to "explain analyze" the problematic queries.
>
> Ciao,
> Thomas
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Query Feromance
@ 2006-03-21 10:58 Thomas Pundt <mlists@rp-online.de>
parent: Marco Furetto <furetto@bluestudio.it>
0 siblings, 0 replies; 7+ messages in thread
From: Thomas Pundt @ 2006-03-21 10:58 UTC (permalink / raw)
To: pgsql-performance
Hi,
On Tuesday 21 March 2006 10:56, Marco Furetto wrote:
| ok, I enable query duration logging in postgresql.conf.
|
| where is the instruments for analyze the statistics queries executing on
| my db?
|
| Eg.: Number of query executing, total time for executing a single query,
| etc...
I don't know if there are tools or settings available for PostgreSQL that do
such number-of-query-accounting; but you can set the
log_min_duration_statement value to 0 to log all statements with their
duration.
See http://www.postgresql.org/docs/8.1/interactive/runtime-config.html
for more options on runtime configuration, especially 17.7 and 17.8
might be of interest for you.
Ciao,
Thomas
--
Thomas Pundt <thomas.pundt@rp-online.de> ---- http://rp-online.de/ ----
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Query Feromance
@ 2006-03-22 09:18 Marco Furetto <furetto@bluestudio.it>
parent: Thomas Pundt <mlists@rp-online.de>
1 sibling, 0 replies; 7+ messages in thread
From: Marco Furetto @ 2006-03-22 09:18 UTC (permalink / raw)
To: pgsql-performance
I find another java program for monitory application query:
http://www.p6spy.com/
with interface
http://www.jahia.net/jahia/page597.html
Thomas Pundt wrote:
> Hi,
>
> On Tuesday 21 March 2006 09:25, Marco Furetto wrote:
> | I'm managing the db of a "Content Management environment" and I'm
> | searching for a "Query analyzer" to improve performance because i don't
> | know how many and what type of queries are executing on the system (for
> | the "where and join" block).
>
> as a first step, I'd enable query duration logging; in postgresql.conf
> I have set
>
> log_min_duration_statement = 3000
>
> this will log each query that needs more than 3 seconds to complete.
>
> The next step would be to "explain analyze" the problematic queries.
>
> Ciao,
> Thomas
>
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2006-03-22 09:18 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-03-20 14:59 Query Feromance Marco Furetto <furetto@bluestudio.it>
2006-03-20 16:34 ` Reimer <carlosreimer@terra.com.br>
2006-03-21 08:25 ` Marco Furetto <furetto@bluestudio.it>
2006-03-21 08:43 ` Thomas Pundt <mlists@rp-online.de>
2006-03-21 09:56 ` Marco Furetto <furetto@bluestudio.it>
2006-03-21 10:58 ` Thomas Pundt <mlists@rp-online.de>
2006-03-22 09:18 ` Marco Furetto <furetto@bluestudio.it>
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