On 30 October 2014 03:30, Etsuro Fujita wrote:
> (2014/10/17 18:35), Etsuro Fujita wrote:
>>
>> (2014/10/16 17:17), Simon Riggs wrote:
>>>
>>> Would it be useful to keep track of how many tables just got analyzed?
>>>
>>> i.e. analyze of foo (including N inheritance children)
>>
>>
>> I think that
(2014/10/17 18:35), Etsuro Fujita wrote:
(2014/10/16 17:17), Simon Riggs wrote:
Would it be useful to keep track of how many tables just got analyzed?
i.e. analyze of foo (including N inheritance children)
I think that's a good idea. So, I'll update the patch.
Done. Attached is an updated
(2014/10/16 17:17), Simon Riggs wrote:
On 16 October 2014 06:49, Etsuro Fujita wrote:
How about this?
automatic analyze of table \"%s.%s.%s\" as inheritance tree
Thank you for the comment.
Would it be useful to keep track of how many tables just got analyzed?
i.e. analyze of foo (incl
On 16 October 2014 06:49, Etsuro Fujita wrote:
> How about this?
>
> automatic analyze of table \"%s.%s.%s\" as inheritance tree
>
> Thank you for the comment.
Would it be useful to keep track of how many tables just got analyzed?
i.e. analyze of foo (including N inheritance children)
--
(2014/10/16 11:45), Simon Riggs wrote:
On 6 October 2014 11:07, Etsuro Fujita wrote:
I noticed that analyze messages shown by autovacuum don't discriminate
between non-inherited cases and inherited cases, as shown in the below
example:
LOG: automatic analyze of table "postgres.public.pt" syst
On 6 October 2014 11:07, Etsuro Fujita wrote:
> I noticed that analyze messages shown by autovacuum don't discriminate
> between non-inherited cases and inherited cases, as shown in the below
> example:
>
> LOG: automatic analyze of table "postgres.public.pt" system usage: CPU
> 0.00s/0.01u sec e
