Re: temporary tables, indexes, and query plans - Mailing list pgsql-performance

From Robert Haas
Subject Re: temporary tables, indexes, and query plans
Date
Msg-id AANLkTi=Rp22xf_c3erEJ2d1FTh_pCQysSCwuVfieGSCd@mail.gmail.com
Whole thread Raw
In response to Re: temporary tables, indexes, and query plans  (Justin Pitts <justinpitts@gmail.com>)
List pgsql-performance
On Wed, Oct 27, 2010 at 3:44 PM, Justin Pitts <justinpitts@gmail.com> wrote:
>> Jason Pitts:
>> RE: changing default_statistics_target (or via ALTER TABLE SET STATS)
>> not taking effect until ANALYZE is performed.
>>
>> I did already know that, but it's probably good to put into this
>> thread. However, you'll note that this is a temporary table created at
>> the beginning of a transaction.
>>
>
> ( giving up on replying to the group; the list will not accept my posts )

Evidently it's accepting some of them...

> I've been following the thread so long I had forgotten that. I rather
> strongly doubt that analyze can reach that table's content inside that
> transaction, if you are creating, populating, and querying it all
> within that single transaction.

Actually I don't think that's a problem, at least for a manual ANALYZE.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: typoed column name, but postgres didn't grump
Next
From: "Kevin Grittner"
Date:
Subject: Re: typoed column name, but postgres didn't grump