Robert Haas wrote:
> On Thu, Apr 8, 2010 at 3:22 PM, Oleg Bartunov wrote:
> >> On general thought I've had is that it would be nice if the first
> >> attempt to SELECT against a table with no statistics would trigger an
> >> automatic ANALYZE by the backend on which the query was executed.
> >> It
On Thu, Apr 8, 2010 at 3:22 PM, Oleg Bartunov wrote:
>> On general thought I've had is that it would be nice if the first
>> attempt to SELECT against a table with no statistics would trigger an
>> automatic ANALYZE by the backend on which the query was executed.
>> It's pretty common to populate
On Thu, 8 Apr 2010, Robert Haas wrote:
On Thu, Apr 8, 2010 at 2:53 PM, Alvaro Herrera
wrote:
Oleg Bartunov wrote:
our client complained about slow query, which involves temporary tables.
Analyzing them manually solved the problem. I don't remember
arguments against temporary tables support b
Robert Haas wrote:
> On Thu, Apr 8, 2010 at 2:53 PM, Alvaro Herrera
>> Autovacuum can't process temp tables; they could reside in a
>> backend's private temp buffers (local memory, not shared).
>
> it would be nice if the first attempt to SELECT against a table
> with no statistics would trigge
On Thu, Apr 8, 2010 at 2:53 PM, Alvaro Herrera
wrote:
> Oleg Bartunov wrote:
>
>> our client complained about slow query, which involves temporary tables.
>> Analyzing them manually solved the problem. I don't remember
>> arguments against temporary tables support by autovacuum. I'd
>> appreciate
Oleg Bartunov wrote:
> our client complained about slow query, which involves temporary tables.
> Analyzing them manually solved the problem. I don't remember
> arguments against temporary tables support by autovacuum. I'd
> appreciate any
> pointers.
Autovacuum can't process temp tables; they co
