From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Justin Pitts <justinpitts(at)gmail(dot)com> |
Cc: | Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: temporary tables, indexes, and query plans |
Date: | 2010-10-29 18:16:02 |
Message-ID: | AANLkTi=Rp22xf_c3erEJ2d1FTh_pCQysSCwuVfieGSCd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Oct 27, 2010 at 3:44 PM, Justin Pitts <justinpitts(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-10-29 18:38:54 | Re: typoed column name, but postgres didn't grump |
Previous Message | Robert Haas | 2010-10-29 18:13:31 | Fwd: failure notice |