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

From tsunakawa.takay@fujitsu.com
Subject RE: When (and whether) should we improve the chapter on parallel query to accommodate parallel data updates?
Date
Msg-id TYAPR01MB29904D33DD98ECFBBFC18148FEAF0@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: When (and whether) should we improve the chapter on parallel query to accommodate parallel data updates?  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
From: Amit Kapila <amit.kapila16@gmail.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
focuseson their features for the moment (parallel insert select, parallel copy, parallel CTAS, etc), and then make the
documentationconsistent 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



pgsql-hackers by date:

Previous
From: "Hou, Zhijie"
Date:
Subject: RE: Single transaction in the tablesync worker?
Next
From: Fujii Masao
Date:
Subject: Re: [PATCH] Feature improvement for CLOSE, FETCH, MOVE tab completion