Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions
От | Dilip Kumar |
---|---|
Тема | Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions |
Дата | |
Msg-id | CAFiTN-sYkK1s=__yhQiVJwN9p0evtWH6b9YVa7yAn=kqxE2HVg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions
|
Список | pgsql-hackers |
On Fri, Jun 12, 2020 at 4:35 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Fri, Jun 12, 2020 at 11:38 AM Dilip Kumar <dilipbalaut@gmail.com> wrote: > > > > - Currently, while reading/writing the streaming/subxact files we are > > reporting the wait event for example > > 'pgstat_report_wait_start(WAIT_EVENT_LOGICAL_SUBXACT_WRITE);', but > > BufFileWrite/BufFileRead internally reports the read/write wait event. > > So I think we can avoid reporting that? > > > > Yes, we can avoid that. No other place using BufFileRead does any > such reporting. I agree. > > Basically, this part is still > > I have to work upon, once we get the consensus then I can remove those > > extra wait event from the patch. > > > > Okay, feel free to send an updated patch with the above change. Sure, I will do that in the next patch set. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: