Skip site navigation (1) Skip section navigation (2)

Re: random_page_cost = 2.0 on Heroku Postgres

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Peter van Hardenberg <pvh(at)pvh(dot)ca>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: random_page_cost = 2.0 on Heroku Postgres
Date: 2012-02-11 16:26:35
Message-ID: CAMkU=1x=p2qSssS65PFrD+8dWhae01x8xxbeV30cZJF8aOyGZQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, Feb 9, 2012 at 2:41 PM, Peter van Hardenberg <pvh(at)pvh(dot)ca> wrote:

> Hmm, perhaps we could usefully aggregate auto_explain output.

By the time you realize the query is running long, it is too late to
start analyzing it.  And without analyzing it, you probably can't get
the information you need.

Maybe with the timing = off feature,it would might make sense to just
preemptively analyze everything.

Cheers,

Jeff

In response to

Responses

pgsql-performance by date

Next:From: Peter van HardenbergDate: 2012-02-11 19:52:28
Subject: Re: random_page_cost = 2.0 on Heroku Postgres
Previous:From: CSSDate: 2012-02-11 06:35:17
Subject: Re: rough benchmarks, sata vs. ssd

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group