RE: When (and whether) should we improve the chapter on parallel query to accommodate parallel data updates?

From: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
To: 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: When (and whether) should we improve the chapter on parallel query to accommodate parallel data updates?
Date: 2021-01-07 01:50:17
Message-ID: TYAPR01MB29904D33DD98ECFBBFC18148FEAF0@TYAPR01MB2990.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> I think each feature should develop the docs as part of feature
> development but if we want to see some additional work like improving
> overall docs for parallel execution as you are suggesting then it can
> be done separately as well.
>
> I think you have a valid point but maybe it would be better to do the
> improvements you are suggesting once the parallel inserts related work
> is committed.
OK. I think at least the words query, statement, execution, and/or operation should be used appropriately before RC (ideally, before beta). Maybe parallel copy should also be put in the chapter. Anyway, I agree that each developer focuses on their features for the moment (parallel insert select, parallel copy, parallel CTAS, etc), and then make the documentation consistent and well-organized after they've settled. (I just felt a bit uneasy to say "this patch looks good" while leaving the document consistency.)

Regards
Takayuki Tsunakawa

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2021-01-07 01:59:28 Re: [PATCH] Feature improvement for CLOSE, FETCH, MOVE tab completion
Previous Message Hou, Zhijie 2021-01-07 01:45:15 RE: Single transaction in the tablesync worker?