Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0FHC-0004h3-JA for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Nov 2022 05:04:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p0FH9-0005j6-T9 for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Nov 2022 05:04:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p0FH9-0005ix-Hw for pgsql-hackers@lists.postgresql.org; Wed, 30 Nov 2022 05:04:51 +0000 Received: from mail-pf1-x436.google.com ([2607:f8b0:4864:20::436]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p0FH2-0003DE-LU for pgsql-hackers@postgresql.org; Wed, 30 Nov 2022 05:04:50 +0000 Received: by mail-pf1-x436.google.com with SMTP id x66so15790206pfx.3 for ; Tue, 29 Nov 2022 21:04:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=DIwEfHJj5ra8UF2HBh5RXfq+zeGuzCtyL6ljTDCBAgU=; b=QzBun17zEb8D5rYRyl+bPnCcyKN5HtPOJadRIKd578pSHyK2oTrUtw+NR/uJZe5q3f TcNHAR68RpQifmdVxdVK3BqmbswhI4BtiP6ICyU8MY5ffUQNfa/wYS5gzLgAZbSY384L zgNt2iawiM7yKN1eH271WjvMcOodMDOLwNkxaGLFsVHm810PvZUVgmr7l0pWeTCcHqvu 5FbBEQZf1pvDYh2weF2+hjchJFEzfcrdJdmhpgF8KGrWTwBQO3o5xFx3bjK/9ISKhJA/ uzaKaErkxkFmYezt01zwHmCruPS9BmOHH3uVoh/ae0xalcDeOY9TLsPKeza/Cp9LzakS 5AuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=DIwEfHJj5ra8UF2HBh5RXfq+zeGuzCtyL6ljTDCBAgU=; b=H9VgiudasWuwPzRT2tXCDHgDKPXu9Fk78cBf74x6GuA6aTN7QGj7pe88RLRWhTLRhg RbkhpZMOeLzS8TRrWlQRUpbvbFZCvGPIC8kah57EBGaaKiPkYM6PeVqgCuYOCyvgg+B2 Q7bGu5AN1LeRMkFw1h8HKHSROyBpgbaJXEPTISS0+4w6Z4fAhgGgPz/8AGF6HD8a09mx UiM9MzAebQuLoOC7d2nmSkmM9+w0ZaegVMDHJhdJLlEoeRw3eo0MD0FjzwbT7bHZnIuS 4Vl+ZDOPmpHUuHrykAGBPPddhK0JW09VqhQ8F9hUMrPKBq37ZS1yVDnBSZ7SC282PnnC pWLg== X-Gm-Message-State: ANoB5plONzKO+IqsSGTAlYf0RynptfqIi+/G/KeHG0/mOG63YREy5oUQ DKMrTcRVF6iobScmP7s0KaM= X-Google-Smtp-Source: AA0mqf53Hv/mBmN6KThkUyyYNOa7874OKCygtxP0CKoI39sHQ2YLJnouq6dWf3tloDF/nvxMgsaXjQ== X-Received: by 2002:a63:d60a:0:b0:476:85ed:5596 with SMTP id q10-20020a63d60a000000b0047685ed5596mr34393471pgg.88.1669784683552; Tue, 29 Nov 2022 21:04:43 -0800 (PST) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id l5-20020a170903244500b00176b3c9693esm206034pls.299.2022.11.29.21.04.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Nov 2022 21:04:42 -0800 (PST) Date: Tue, 29 Nov 2022 21:04:41 -0800 From: Nathan Bossart To: Thomas Munro Cc: "Hayato Kuroda (Fujitsu)" , "pgsql-hackers@postgresql.org" Subject: Re: wake up logical workers after ALTER SUBSCRIPTION Message-ID: <20221130050441.GA1677223@nathanxps13> References: <20221122043916.GA230228@nathanxps13> <20221123205027.GA368966@nathanxps13> <20221127234528.GB878043@nathanxps13> <20221130041028.GA1604177@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Nov 30, 2022 at 05:27:40PM +1300, Thomas Munro wrote: > On Wed, Nov 30, 2022 at 5:23 PM Thomas Munro wrote: >> On Wed, Nov 30, 2022 at 5:10 PM Nathan Bossart wrote: >> > I spent some more time on the prevent-unnecessary-wakeups patch for >> > logical/worker.c that I've been alluding to in this thread, and I found a >> > few more places where we depend on the worker periodically waking up. This >> > seems to be a common technique, so I'm beginning to wonder whether these >> > changes are worthwhile. I think there's a good chance it would become a >> > game of whac-a-mole. >> >> Aren't they all bugs, though, making our tests and maybe even real >> systems slower than they need to be? Yeah, you're right, it's probably worth proceeding with this particular thread even if we don't end up porting the suppress-unnecessary-wakeups patch to logical/worker.c. > (Which isn't to suggest that it's your job to fix them, but please do > share what you have if you run out of whack-a-mole steam, since we > seem to have several people keen to finish those moles off.) I don't mind fixing it! There are a couple more I'd like to track down before posting another revision. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com