Subject: Re: [GENERAL] ANALYZE after CREATE TABLE AS SELECT...
On 2/26/15 2:05 PM, Tom Lane wrote:
> "Semyon Reyfman" writes:
>> When I create a table with "CREATE TABLE name AS SELECT." statement
>> and immediately afterward use this new table in a query does
David Steele writes:
> On 2/26/15 5:23 PM, Alvaro Herrera wrote:
>> It isn't. It also doesn't create any indexes, which you might want to
>> do before analyze.
> Is it necessary to create indexes before analyzing?
> I usually do, just to be safe, but I thought statistics were based
> solely on
On 2/26/15 5:23 PM, Alvaro Herrera wrote:
> Semyon Reyfman wrote:
>
>> When I create a table with "CREATE TABLE name AS SELECT." statement and
>> immediately afterward use this new table in a query does it make sense to
>> run ANALYZE on the table in between? It appears that postgres should be
>>
On 2/26/15 2:05 PM, Tom Lane wrote:
> "Semyon Reyfman" writes:
>> When I create a table with "CREATE TABLE name AS SELECT." statement and
>> immediately afterward use this new table in a query does it make sense to
>> run ANALYZE on the new table in between?
>
> Yes.
Yes. And to be more specifi
Semyon Reyfman wrote:
> When I create a table with "CREATE TABLE name AS SELECT." statement and
> immediately afterward use this new table in a query does it make sense to
> run ANALYZE on the table in between? It appears that postgres should be
> able to collect very detailed statistics while em
"Semyon Reyfman" writes:
> When I create a table with "CREATE TABLE name AS SELECT." statement and
> immediately afterward use this new table in a query does it make sense to
> run ANALYZE on the new table in between?
Yes.
regards, tom lane
--
Sent via pgsql-general ma
