On Tue, Feb 5, 2013 at 01:41:05PM +0530, Pavan Deolasee wrote:
> On Fri, Feb 1, 2013 at 10:53 PM, Bruce Momjian wrote:
> >
> >
> > Are these TODO items?
> >
>
> BTW, there are couple of TODOs.
>
> 1. Analyze should be done based on the total row churn across the
> parent + children. Looking a
On Fri, Feb 1, 2013 at 10:53 PM, Bruce Momjian wrote:
>
>
> Are these TODO items?
>
BTW, there are couple of TODOs.
1. Analyze should be done based on the total row churn across the
parent + children. Looking at the parent only, as we do now, can
result in analyzing too often or too seldom.
2
On Mon, Feb 4, 2013 at 9:05 PM, Robert Haas wrote:
> On Fri, Feb 1, 2013 at 12:33 PM, Pavan Deolasee
> wrote:
>> I can write a patch in next couple of days if we are willing to accept
>> for this release. I think it should be fairly easy and non-intrusive.
>
> I think it's too late to consider th
On Fri, Feb 1, 2013 at 12:33 PM, Pavan Deolasee
wrote:
> I can write a patch in next couple of days if we are willing to accept
> for this release. I think it should be fairly easy and non-intrusive.
I think it's too late to consider this for 9.3, but I think we should
entertain it for 9.4.
The
On Fri, Feb 1, 2013 at 5:54 PM, Pavan Deolasee wrote:
> There is another problem that I noticed while looking at this case.
> The analyze took close to 500sec on a fairly good hardware (40GB RAM,
> 10K rpm disks on RAID10) because many large child tables were scanned
> at once.
>
Just a small cor
On Fri, Feb 1, 2013 at 10:53 PM, Bruce Momjian wrote:
> On Fri, Feb 1, 2013 at 12:37:21PM -0300, Alvaro Herrera wrote:
>
>> > A new reloption such as autovacuum_analyze_enabled is what we need.
>>
>> I was thinking in this option just three days ago, so yeah.
>>
>> I think we also want an option
On Fri, Feb 1, 2013 at 12:37:21PM -0300, Alvaro Herrera wrote:
> Pavan Deolasee escribió:
>
> > While looking at this particular case on -general, I realized that there is
> > no way to *only* disable auto-analyze on a table. While one can cheat like
> > what I suggested to the OP by setting thre
On Fri, Feb 1, 2013 at 9:07 PM, Alvaro Herrera wrote:
> Pavan Deolasee escribió:
>
>>
>> A new reloption such as autovacuum_analyze_enabled is what we need.
>
> I was thinking in this option just three days ago, so yeah.
>
> I think we also want an option to turn off just vacuum.
>
+1. I think th
On Fri, Feb 1, 2013 at 9:04 PM, Tom Lane wrote:
> Pavan Deolasee writes:
>> A new reloption such as autovacuum_analyze_enabled is what we need.
>
> This seems to me to be a wart that doesn't fix the actual problem ---
IMHO this case is just an example, but I'm sure there would be similar
such e
Pavan Deolasee escribió:
> While looking at this particular case on -general, I realized that there is
> no way to *only* disable auto-analyze on a table. While one can cheat like
> what I suggested to the OP by setting threshold very high, I think it will
> be useful to be able to just off analyz
Pavan Deolasee writes:
> While looking at this particular case on -general, I realized that there is
> no way to *only* disable auto-analyze on a table. While one can cheat like
> what I suggested to the OP by setting threshold very high, I think it will
> be useful to be able to just off analyze.
11 matches
Mail list logo
