| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, alvherre(at)alvh(dot)no-ip(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Suppressing useless wakeups in walreceiver |
| Date: | 2022-11-09 04:52:37 |
| Message-ID: | CALj2ACUXx6Qkv-zfHrFF5=VkJ7se8+At2KqQSX5pp27mvKziwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 9, 2022 at 2:38 AM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> On Tue, Nov 08, 2022 at 09:45:40PM +1300, Thomas Munro wrote:
> > On Tue, Nov 8, 2022 at 9:20 PM Bharath Rupireddy
> > <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> >> Thanks. Do we need a similar wakeup approach for logical replication
> >> workers in worker.c? Or is it okay that the nap time is 1sec there?
> >
> > Yeah, I think so. At least for its idle/nap case (waiting for flush
> > is also a technically interesting case, but harder, and applies to
> > non-idle systems so the polling is a little less offensive).
>
> Bharath, are you planning to pick this up? If not, I can probably spend
> some time on it.
Please go ahead!
--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-11-09 05:04:00 | Re: Improve logging when using Huge Pages |
| Previous Message | Michael Paquier | 2022-11-09 04:52:15 | Re: allow segment size to be set to < 1GiB |