public inbox for [email protected]
help / color / mirror / Atom feedFrom: [email protected] <[email protected]>
To: [email protected] <[email protected]>
Cc: Dilip Kumar <[email protected]>
Cc: Masahiko Sawada <[email protected]>
Cc: [email protected] <[email protected]>
Cc: Peter Smith <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: [email protected] <[email protected]>
Cc: 'Amit Kapila' <[email protected]>
Subject: RE: Perform streaming logical transactions by background workers and parallel apply
Date: Thu, 6 Oct 2022 12:11:15 +0000
Message-ID: <OS0PR01MB57161EB97DF028B286DBEADC945C9@OS0PR01MB5716.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TYAPR01MB58669BC62F5E504E8E246C28F55C9@TYAPR01MB5866.jpnprd01.prod.outlook.com>
References: <OS0PR01MB5716730C06159452335D870D947F9@OS0PR01MB5716.jpnprd01.prod.outlook.com>
<CAA4eK1Lu-6oXMk7ZaGYLwm3CRLBuzueGbasyHnNpJxu6Mq3mmg@mail.gmail.com>
<OS3PR01MB6275F145878B4A44586C46CE9E499@OS3PR01MB6275.jpnprd01.prod.outlook.com>
<CAA4eK1LMVdS6uM7Tw7ANL0BetAd76TKkmAXNNQa0haTe2tax6g@mail.gmail.com>
<OS3PR01MB6275EFC4B707650DAB9392859E4D9@OS3PR01MB6275.jpnprd01.prod.outlook.com>
<CAHut+PuVjRgGr4saN7qwq0oB8DANHVR7UfDiciB1Q3cYN54F6A@mail.gmail.com>
<OS3PR01MB627567CF4B96A23DAFAF77269E4E9@OS3PR01MB6275.jpnprd01.prod.outlook.com>
<TYAPR01MB5866727DCFC8B47FAC46ABF6F54E9@TYAPR01MB5866.jpnprd01.prod.outlook.com>
<OS3PR01MB6275F4A7CA186412E2FF2ED29E529@OS3PR01MB6275.jpnprd01.prod.outlook.com>
<TYAPR01MB586669F3243F2F399712FC98F5529@TYAPR01MB5866.jpnprd01.prod.outlook.com>
<TYAPR01MB58662D8CEC97E774FCE62F05F5559@TYAPR01MB5866.jpnprd01.prod.outlook.com>
<OS0PR01MB57162BC6B0FB848F216410DE94559@OS0PR01MB5716.jpnprd01.prod.outlook.com>
<TYAPR01MB58664D1D5B40689769386873F5579@TYAPR01MB5866.jpnprd01.prod.outlook.com>
<CAA4eK1JJNbQGcBsQiXdSzwneeBwj4WJ8ZibDPN2CLA_uP38UJw@mail.gmail.com>
<TYAPR01MB58669BC62F5E504E8E246C28F55C9@TYAPR01MB5866.jpnprd01.prod.outlook.com>
On Thursday, October 6, 2022 6:54 PM Kuroda, Hayato/黒田 隼人 <[email protected]> wrote:
>
> Dear Amit,
>
> > Can't we use WaitLatch in the case of SHM_MQ_WOULD_BLOCK as we are
> > using it for the same case at some other place in the code? We can use
> > the same nap time as we are using in the leader apply worker.
>
> I'm not sure whether such a short nap time is needed or not.
> Because unlike leader apply worker, parallel apply workers do not have timeout
> like wal_receiver_timeout, so they do not have to check so frequently and send
> feedback to publisher.
> But basically I agree that we can use same logic as leader.
Thanks for the suggestion.
I tried to add a WaitLatch, but it seems affect the performance
because the Latch might not be set when leader send some
message to parallel apply worker which means it will wait until
timeout.
I feel we'd better change it back to sync mode and do the ProcessConfigFile()
after receiving the message and before applying the change which seems also
address the problem.
Best regards,
Hou zj
view thread (625+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: RE: Perform streaming logical transactions by background workers and parallel apply
In-Reply-To: <OS0PR01MB57161EB97DF028B286DBEADC945C9@OS0PR01MB5716.jpnprd01.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox