Re: parallel index creation: maintenance_work_mem not honored?

From: Fabio Pardi <f(dot)pardi(at)portavita(dot)eu>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: parallel index creation: maintenance_work_mem not honored?
Date: 2022-06-21 05:38:17
Message-ID: 7441b023-5b3f-6646-0261-c53556f91b3a@portavita.eu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Thanks Peter for your answer,

On 20/06/2022 17:47, Peter Geoghegan wrote:
>
> Yes, this is expected. Parallel CREATE INDEX performs its parallel
> sort by having workers generate sorted runs, which are written to temp
> files, and then having the leader process merge the sorted runs
> together as the index is built.

Just to make sure we are on the same page: every parallel 'CREATE INDEX' writes to temp files, ok.

But why the temp files are always on disk and not in RAM as other operations do?

> In the case where there is amble maintenance_work_mem, all writes to
> and reads from temp files will be sequential.
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Geoghegan 2022-06-21 05:46:52 Re: parallel index creation: maintenance_work_mem not honored?
Previous Message Teja Jakkidi 2022-06-21 05:27:46 Re: Inactive replication slots