Re: Parallel COPY FROM execution

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Alex K <kondratov(dot)aleksey(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Anastasia Lubennikova <lubennikovaAV(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Parallel COPY FROM execution
Date: 2017-10-02 08:54:34
Message-ID: 251EC7D5-E547-4268-A96E-DF54A3766947@yesql.se
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

> On 11 Aug 2017, at 20:07, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Fri, Aug 11, 2017 at 9:55 AM, Alex K <kondratov(dot)aleksey(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2017-10-02 09:31:07 Re: PATCH: Batch/pipelining support for libpq
Previous Message Kyotaro HORIGUCHI 2017-10-02 08:23:34 Re: [PATCH] Improve geometric types