Re: temporary tables, indexes, and query plans

From: Justin Pitts <justinpitts(at)gmail(dot)com>
To: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: temporary tables, indexes, and query plans
Date: 2010-10-27 19:44:52
Message-ID: AANLkTi=waPo8pySeh8DGOztLjhev3rWoNX3DXEA+WO19@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> 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 )
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.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alex Hunsaker 2010-10-27 19:45:06 Re: Postgres insert performance and storage requirement compared to Oracle
Previous Message Tom Lane 2010-10-27 19:43:13 Re: temporary tables, indexes, and query plans