On 12 February 2012 22:28, Peter van Hardenberg wrote:
> Yes, I think if we could normalize, anonymize, and randomly EXPLAIN
> ANALYZE 0.1% of all queries that run on our platform we could look for
> bad choices by the planner. I think the potential here could be quite
> remarkable.
Tom Lane sugg
On Sun, Feb 12, 2012 at 12:01 PM, Joshua Berkus wrote:
> You'd pretty much need to do large-scale log harvesting combined with samples
> of query concurrency taken several times per minute. Even that won't
> "normalize" things the way you want, though, since all queries are not equal
> in term
> Is there an easy and unintrusive way to get such a metric as the
> aggregated query times? And to normalize it for how much work
> happens
> to have been doing on at the time?
You'd pretty much need to do large-scale log harvesting combined with samples
of query concurrency taken several time
On Thu, Feb 9, 2012 at 5:29 PM, Scott Marlowe wrote:
> On Thu, Feb 9, 2012 at 3:41 PM, Peter van Hardenberg wrote:
>> Hmm, perhaps we could usefully aggregate auto_explain output.
>
> How about something where you run a site at random_page cost of x,
> then y, then z and you do some aggregating o
Frank Lanitz wrote:
> Am 12.02.2012 11:48, schrieb Ofer Israeli:
>> Frank Lanitz wrote:
Am 07.02.2012 18:40, schrieb Ofer Israeli:
>> Table 1: 46 columns 23 indexes on fields of the following
>> types: INTEGER - 7 TIMESTAMP - 2 VARCHAR - 12 UUID - 2
>>
>> 23 columns 12 indexes
Am 12.02.2012 11:48, schrieb Ofer Israeli:
> Frank Lanitz wrote:
>>> Am 07.02.2012 18:40, schrieb Ofer Israeli:
> Table 1: 46 columns 23 indexes on fields of the following
> types: INTEGER - 7 TIMESTAMP - 2 VARCHAR - 12 UUID - 2
>
> 23 columns 12 indexes on fields of the following
Frank Lanitz wrote:
> Am 07.02.2012 18:40, schrieb Ofer Israeli:
>> Table 1:
>> 46 columns
>> 23 indexes on fields of the following types:
>> INTEGER - 7
>> TIMESTAMP - 2
>> VARCHAR - 12
>> UUID - 2
>>
>> 23 columns
>> 12 indexes on fields of the following types:
>> INTEGER - 3
>> TIMESTAMP - 1
>>
