>I ask your help to solve a slow query which is taking more than 14 seconds to
>be executed.
>Maybe I am asking too much both from you and specially from postgresql, as it
>is really huge, envolving 16 tables.
>
>Explain:
>http://explain.depesz.com/s/XII9
>
>Schema:
Hi,
I ask your help to solve a slow query which is taking more than 14
seconds to be executed.
Maybe I am asking too much both from you and specially from postgresql,
as it is really huge, envolving 16 tables.
Explain:
http://explain.depesz.com/s/XII9
Schema:
On Tue, Feb 5, 2013 at 9:15 AM, Will Platnick wplatn...@gmail.com wrote:
We upgraded from PG 9.1 to 9.2. Since the upgrade, the # of active queries
has raised significantly, especially during our peak time where lots of
users are logging in. According to New Relic, this query is now taking up
Good eye, I totally missed that!
Any ideas on how to troubleshoot this delay?
On Wednesday, February 6, 2013 at 3:51 AM, Pavan Deolasee wrote:
On Tue, Feb 5, 2013 at 9:15 AM, Will Platnick wplatn...@gmail.com
(mailto:wplatn...@gmail.com) wrote:
We upgraded from PG 9.1 to 9.2. Since the
Will Platnick wplatn...@gmail.com wrote:
Will Platnick wplatn...@gmail.com wrote:
The only thing that stands out is: on your production server I see
Total runtime: 7.515 ms, but the top node in EXPLAIN ANAYZE shows
actual time as 0.179 ms. Not sure where that additional time is being
spent
Clients are technically our pgbouncer which is on the same machine. The explain
analyze was local through psql direct to postgresql.
On Wednesday, February 6, 2013 at 11:22 AM, Kevin Grittner wrote:
Will Platnick wplatn...@gmail.com (mailto:wplatn...@gmail.com) wrote:
Will Platnick
On Wed, Feb 6, 2013 at 9:52 PM, Kevin Grittner kgri...@ymail.com wrote:
Will Platnick wplatn...@gmail.com wrote:
Will Platnick wplatn...@gmail.com wrote:
The only thing that stands out is: on your production server I see
Total runtime: 7.515 ms, but the top node in EXPLAIN ANAYZE shows
On 05.02.2013 05:45, Will Platnick wrote:
We upgraded from PG 9.1 to 9.2. Since the upgrade, the # of active queries has
raised significantly, especially during our peak time where lots of users are
logging in. According to New Relic, this query is now taking up the most
amount of time
We upgraded from PG 9.1 to 9.2. Since the upgrade, the # of active queries has
raised significantly, especially during our peak time where lots of users are
logging in. According to New Relic, this query is now taking up the most
amount of time during peak activity and my pg_stat_activity and
