From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | maintenance_work_mem and CREATE INDEX time |
Date: | 2013-07-23 04:11:45 |
Message-ID: | CA+HiwqGNRGQCh0vyhcHVbuWjchQU3E7L9uzyZtsuWvyf_jqH6g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Hello,
While understanding the effect of maintenance_work_mem on time taken
by CREATE INDEX, I observed that for the values of
maintenance_work_mem less than the value for which an internal sort is
performed, the time taken by CREATE INDEX increases as
maintenance_work_increases.
My guess is that for all those values an external sort is chosen at
some point and larger the value of maintenance_work_mem, later the
switch to external sort would be made causing CREATE INDEX to take
longer. That is a smaller value of maintenance_work_mem would be
preferred for when external sort is performed anyway. Does that make
sense?
--
Amit Langote
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2013-07-23 08:23:58 | Re: maintenance_work_mem and CREATE INDEX time |
Previous Message | Natalie Wenz | 2013-07-22 21:47:21 | Re: Insert result does not match record count |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-07-23 04:14:07 | Re: proposal - psql - show longest tables |
Previous Message | Pavel Stehule | 2013-07-23 04:08:58 | Re: proposal - psql - show longest tables |