When checking the result of pt-query_digest, I noticed column *query_review.first_seen *and *query_review_history.ts_min* always have the same value. Do they actually have any difference?
They can have the same value, but not always. The query_review table keeps
unique instances of each query, but the query_review_history can have
multiple entries for each query fingerprint. The fields ts_min and ts_max
are the statistics aggregated for that query in that particular duration of
time. I'm not sure what the original author intended with the abbreviation
ts_, but I think of it as "time slice" or "time series."
In the query_review table, there's only one entry per unique query
fingerprint, and the values for first_seen and last_seen are updated with
the smallest value of ts_min for any record in the history table, and
last_seen has the highest value of any ts_max value.
On Mon, Sep 24, 2012 at 6:32 AM, Jacky Shu <jackys...@gmail.com> wrote:
> Hi,
> When checking the result of pt-query_digest, I noticed column *query_review.first_seen
> *and *query_review_history.ts_min* always have the same value.
> Do they actually have any difference?
> Thanks.
> --
> You received this message because you are subscribed to the Google Groups
> "Percona Discussion" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/percona-discussion/-/5ay0J6vzWuIJ.
> To post to this group, send email to percona-discussion@googlegroups.com.
> To unsubscribe from this group, send email to
> percona-discussion+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/percona-discussion?hl=en.
On Monday, September 24, 2012 1:36:35 PM UTC-4, Gavin Towey wrote:
> Hi Jacky,
> They can have the same value, but not always. The query_review table > keeps unique instances of each query, but the query_review_history can have > multiple entries for each query fingerprint. The fields ts_min and ts_max > are the statistics aggregated for that query in that particular duration of > time. I'm not sure what the original author intended with the abbreviation > ts_, but I think of it as "time slice" or "time series."
> In the query_review table, there's only one entry per unique query > fingerprint, and the values for first_seen and last_seen are updated with > the smallest value of ts_min for any record in the history table, and > last_seen has the highest value of any ts_max value.
> Regards, > Gavin Towey
> On Mon, Sep 24, 2012 at 6:32 AM, Jacky Shu <jack...@gmail.com<javascript:> > > wrote:
>> Hi,
>> When checking the result of pt-query_digest, I noticed column *query_review.first_seen >> *and *query_review_history.ts_min* always have the same value. >> Do they actually have any difference?
>> Thanks.
>> -- >> You received this message because you are subscribed to the Google Groups >> "Percona Discussion" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/percona-discussion/-/5ay0J6vzWuIJ. >> To post to this group, send email to percona-d...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> percona-discussion+unsubscribe@googlegroups.com <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/percona-discussion?hl=en.
Hi Gavin, Sorry have to ask you again, what is the meaning of query_review_history.*ts_cnt *column? I thought it was how many times a query ran, but it was wrong.
On Tuesday, September 25, 2012 12:32:01 PM UTC-4, Jacky Shu wrote:
> Thanks Gavin. > Guess I should have used a query to check whether they have same value!
> On Monday, September 24, 2012 1:36:35 PM UTC-4, Gavin Towey wrote:
>> Hi Jacky,
>> They can have the same value, but not always. The query_review table >> keeps unique instances of each query, but the query_review_history can have >> multiple entries for each query fingerprint. The fields ts_min and ts_max >> are the statistics aggregated for that query in that particular duration of >> time. I'm not sure what the original author intended with the abbreviation >> ts_, but I think of it as "time slice" or "time series."
>> In the query_review table, there's only one entry per unique query >> fingerprint, and the values for first_seen and last_seen are updated with >> the smallest value of ts_min for any record in the history table, and >> last_seen has the highest value of any ts_max value.
>> Regards, >> Gavin Towey
>> On Mon, Sep 24, 2012 at 6:32 AM, Jacky Shu <jack...@gmail.com> wrote:
>>> Hi,
>>> When checking the result of pt-query_digest, I noticed column *query_review.first_seen >>> *and *query_review_history.ts_min* always have the same value. >>> Do they actually have any difference?
>>> Thanks.
>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Percona Discussion" group. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msg/percona-discussion/-/5ay0J6vzWuIJ. >>> To post to this group, send email to percona-d...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> percona-discussion+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/percona-discussion?hl=en.
ts_cnt is indeed the count of instances of that query found in that time
interval. What are you seeing that makes it look like that isn't true for
you?
On Tue, Sep 25, 2012 at 9:46 AM, Jacky Shu <jackys...@gmail.com> wrote:
> Hi Gavin,
> Sorry have to ask you again, what is the meaning of query_review_history.
> *ts_cnt *column?
> I thought it was how many times a query ran, but it was wrong.
> Thanks
> On Tuesday, September 25, 2012 12:32:01 PM UTC-4, Jacky Shu wrote:
>> Thanks Gavin.
>> Guess I should have used a query to check whether they have same value!
>> On Monday, September 24, 2012 1:36:35 PM UTC-4, Gavin Towey wrote:
>>> Hi Jacky,
>>> They can have the same value, but not always. The query_review table
>>> keeps unique instances of each query, but the query_review_history can have
>>> multiple entries for each query fingerprint. The fields ts_min and ts_max
>>> are the statistics aggregated for that query in that particular duration of
>>> time. I'm not sure what the original author intended with the abbreviation
>>> ts_, but I think of it as "time slice" or "time series."
>>> In the query_review table, there's only one entry per unique query
>>> fingerprint, and the values for first_seen and last_seen are updated with
>>> the smallest value of ts_min for any record in the history table, and
>>> last_seen has the highest value of any ts_max value.
>>> Regards,
>>> Gavin Towey
>>> On Mon, Sep 24, 2012 at 6:32 AM, Jacky Shu <jack...@gmail.com> wrote:
>>>> Hi,
>>>> When checking the result of pt-query_digest, I noticed column *query_review.first_seen
>>>> *and *query_review_history.ts_min* always have the same value.
>>>> Do they actually have any difference?
> To post to this group, send email to percona-discussion@googlegroups.com.
> To unsubscribe from this group, send email to
> percona-discussion+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/percona-discussion?hl=en.
On Tuesday, September 25, 2012 1:45:11 PM UTC-4, Gavin Towey wrote:
> ts_cnt is indeed the count of instances of that query found in that time > interval. What are you seeing that makes it look like that isn't true for > you?
> On Tue, Sep 25, 2012 at 9:46 AM, Jacky Shu <jack...@gmail.com<javascript:> > > wrote:
>> Hi Gavin, >> Sorry have to ask you again, what is the meaning of query_review_history. >> *ts_cnt *column? >> I thought it was how many times a query ran, but it was wrong.
>> Thanks
>> On Tuesday, September 25, 2012 12:32:01 PM UTC-4, Jacky Shu wrote:
>>> Thanks Gavin. >>> Guess I should have used a query to check whether they have same value!
>>> On Monday, September 24, 2012 1:36:35 PM UTC-4, Gavin Towey wrote:
>>>> Hi Jacky,
>>>> They can have the same value, but not always. The query_review table >>>> keeps unique instances of each query, but the query_review_history can have >>>> multiple entries for each query fingerprint. The fields ts_min and ts_max >>>> are the statistics aggregated for that query in that particular duration of >>>> time. I'm not sure what the original author intended with the abbreviation >>>> ts_, but I think of it as "time slice" or "time series."
>>>> In the query_review table, there's only one entry per unique query >>>> fingerprint, and the values for first_seen and last_seen are updated with >>>> the smallest value of ts_min for any record in the history table, and >>>> last_seen has the highest value of any ts_max value.
>>>> Regards, >>>> Gavin Towey
>>>> On Mon, Sep 24, 2012 at 6:32 AM, Jacky Shu <jack...@gmail.com> wrote:
>>>>> Hi,
>>>>> When checking the result of pt-query_digest, I noticed column *query_review.first_seen >>>>> *and *query_review_history.ts_min* always have the same value. >>>>> Do they actually have any difference?
>> To post to this group, send email to percona-d...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> percona-discussion+unsubscribe@googlegroups.com <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/percona-discussion?hl=en.
