Re: [HACKERS] Parallel COPY FROM execution
| От | Daniel Gustafsson | 
|---|---|
| Тема | Re: [HACKERS] Parallel COPY FROM execution | 
| Дата | |
| Msg-id | 251EC7D5-E547-4268-A96E-DF54A3766947@yesql.se обсуждение исходный текст  | 
		
| Ответ на | Re: [HACKERS] Parallel COPY FROM execution (Robert Haas <robertmhaas@gmail.com>) | 
| Список | pgsql-hackers | 
> On 11 Aug 2017, at 20:07, Robert Haas <robertmhaas@gmail.com> wrote: > > On Fri, Aug 11, 2017 at 9:55 AM, Alex K <kondratov.aleksey@gmail.com> wrote: >> - I have used both Latch and ConditionalVariable for the same >> purpose–wait until some signal >> occurs–and for me as an end user they perform quite similar. I >> looked into the condition_variable.c >> code and it uses Latch and SpinLock under the hood. So what are >> differences and dis-/advantages >> between Latch and ConditionalVariable? > > A ConditionVariable lets you signal the processes that are waiting > without needing to know in advance exactly which processes those are. > If you use latches directly, you'll have to somehow keep track of > which processes need to be signaled. Based on the discussion in this thread, and that a new version of the patch hasn’t been submitted during the commitfest, I’m marking this Returned with Feedback. Please re-submit a new version in an upcoming commitfest. cheers ./daniel -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: