Re: Asynchronous MergeAppend - Mailing list pgsql-hackers

From Alexander Pyhalov
Subject Re: Asynchronous MergeAppend
Date
Msg-id 10c97af0ce34ebdb81708b1c49ed6038@postgrespro.ru
Whole thread Raw
In response to Re: Asynchronous MergeAppend  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Asynchronous MergeAppend
List pgsql-hackers
Hi.

Looked at it. Overall I agree that when we wait for data from one slot 
after node initialization, we can't get data from other slots - they are 
already either exhausted, or have already received data which is not 
needed for now. So it seems that async machinery on later stages is 
useless.

Was a bit surprised that asyncresults field is not used in async merge 
append anymore, as we save result directly in ms_slots. However, as we 
do it only on initial stage, this seems to be OK.

classify_matching_subplans() comment still refers to ms_valid_subplans.

Will look at it once again tomorrow.
-- 
Best regards,
Alexander Pyhalov,
Postgres Professional



pgsql-hackers by date:

Previous
From: David Geier
Date:
Subject: Re: Reduce build times of pg_trgm GIN indexes
Next
From: Kirill Reshke
Date:
Subject: Re: DELETE/UPDATE FOR PORTION OF with rule system is not working