Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sduaV-00290Q-Up for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Aug 2024 16:41:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sduZV-00597b-Se for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Aug 2024 16:40:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sduZV-00597R-I5 for pgsql-hackers@lists.postgresql.org; Tue, 13 Aug 2024 16:40:33 +0000 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sduZS-004ZFz-Ng for pgsql-hackers@postgresql.org; Tue, 13 Aug 2024 16:40:32 +0000 Received: by mail-io1-xd33.google.com with SMTP id ca18e2360f4ac-81fd520fee5so229565439f.2 for ; Tue, 13 Aug 2024 09:40:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723567230; x=1724172030; darn=postgresql.org; 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=S/Rh0SQmrfuQ+s63cq0hCaW8krqf4ULa6D/GuxHCrL0=; b=N6wTg7dLaDDN3dVu+9zAiiPNIInlbNvbpQDFGg9ctHJ3ucWweIDLuJDW9S6JdZrQ02 r7pRjEadvN3GcNtD/U+d7jWFRu+28lj7bAF8a8ElMKZnAQxyUq4If6f2Kyp1owX4jL+C HziBuiJwwNklP/h2Z7qNGHe7KxW3LDrj/E6r0f4YMHTgbuM3mqy9dzoxxD4gFrKxmFT+ OLxMcXWF1l9jX/5/46hQUbIL3tzk4T2m9WXg2/YgLNFYq4ziacNB0vfqOpzdNI5N3+cO px5v8g1fzWGpH9aZvjzg+jNZX1HhApUic9Z+GhhCXzJCJxPnbZH3+XE+t1XM9SC463TM cWVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723567230; x=1724172030; 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=S/Rh0SQmrfuQ+s63cq0hCaW8krqf4ULa6D/GuxHCrL0=; b=DPBhcOBE0KK/H5ToOOanzDXDBH9LQRb6a4lnfzU4ia17QqUgpOu8IxEgFkktk4mFX2 FXzz1HOX27i1Muy9L1fr5Cam4RDiSTZALVP/ffXKZ8ugpwpS2311k3aUDVGnSY84N/BQ 6K8ev/3GpZIstxu9ZNnMKid0/6iYRB6pGa7+XTA8ymUwV7BRnayRDJu39CXslcEZS889 JRLQ6aYTdTZ6rHJ8a9a9rWr0s/qoA6C8YYX3pC+HWvYqcdChzHFR7qa56jtKJ9iZ4CLK bqsV7r6uYsD+5I7ImbIaTBTh6VQhsRiBS+lPprdUrH+eTYP96v8/uUT0SNq6tVaLEMXr RhTw== X-Forwarded-Encrypted: i=1; AJvYcCVTpRrz6Sjdex+SfDL4dQ1z5SpHAQZCg/z/zoAPpqFj0/vB83ySUQ/Bs1lwlh95z0Yyp2ldVxhJHBsQTRdoc+HsYdbhK8iE+OyxYsGJ X-Gm-Message-State: AOJu0YzB8m1Wt4sm3sI1kmQdqmltdKJWaFNMdPjw5W9P+ZSZUNvmz7Qy SuyqzdSTUpJiu4WxuQaGtA81gkV/XOJXn3j/zUPwjWiijiIyrllK X-Google-Smtp-Source: AGHT+IHSDHLW7wFGt2S2NbwD44AILeESKwD5aa0lcc4zULReoJq8RAnjOFX3PTNZmioHf6OvKCSsuQ== X-Received: by 2002:a05:6602:6c09:b0:805:3d47:19cf with SMTP id ca18e2360f4ac-824dadd02dfmr19407839f.15.1723567229921; Tue, 13 Aug 2024 09:40:29 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id ca18e2360f4ac-8226720ce9fsm267163339f.4.2024.08.13.09.40.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 13 Aug 2024 09:40:29 -0700 (PDT) Date: Tue, 13 Aug 2024 11:40:27 -0500 From: Nathan Bossart To: "Imseih (AWS), Sami" Cc: Heikki Linnakangas , Bertrand Drouvot , Tom Lane , Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: Restart pg_usleep when interrupted Message-ID: References: <2b5ac681-11d5-470d-af40-89ead9a868aa@gmail.com> <90ec1618-58db-46b3-8c9b-13616ac839a7@gmail.com> 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 Tue, Aug 13, 2024 at 11:07:46AM -0500, Imseih (AWS), Sami wrote: > Having to add special handling to space out instrumentation > directly in vacuum_delay_point seems very odd to me. I don't > think vacuum_delay_point should have to worry about this. > > Also, > 1/ what is an appropriate interval to collect these stats? > 2/ What if there are other callers in the future that wish > to instrument parallel vacuum workers? they will need to implement > similar logic. None of this seems intractable to me. 1 Hz seems like an entirely reasonable place to start, and it is very easy to change (or to even make configurable). pg_stat_progress_vacuum might show slightly old values in this column, but that should be easy enough to explain in the docs if we are really concerned about it. If other callers want to do something similar, maybe we should add a more generic implementation in backend_progress.c. -- nathan