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 1rmFF8-006qQa-WD for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Mar 2024 15:49:43 +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 1rmFF7-003TW3-G7 for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Mar 2024 15:49:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rmFF6-003TVu-V7 for pgsql-hackers@lists.postgresql.org; Mon, 18 Mar 2024 15:49:41 +0000 Received: from mail-ot1-x32e.google.com ([2607:f8b0:4864:20::32e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rmFF4-005Cnp-Pl for pgsql-hackers@lists.postgresql.org; Mon, 18 Mar 2024 15:49:40 +0000 Received: by mail-ot1-x32e.google.com with SMTP id 46e09a7af769-6ddca59e336so2251591a34.0 for ; Mon, 18 Mar 2024 08:49:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1710776977; x=1711381777; darn=lists.postgresql.org; h=user-agent: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=eoBhWKeumGgAiR1sxndatZ/N2mKQX5+wr+PZ8gBG4dM=; b=NptdiGXS7ilNtVV+TLSH9CBx944ocOrGYdUYOljm4MUVVG+73N3FkZVj31Yl8NqCKp WbniwhzgtkyYSTqPTmpHEjq2cxHy9P/3j4yXkBjywmqbheNhfCd5Dgpc8H9jyLi1zPPc eVtn48/VqA3EyU63eFa94fEKsF5lYidCFTrmI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710776977; x=1711381777; h=user-agent: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=eoBhWKeumGgAiR1sxndatZ/N2mKQX5+wr+PZ8gBG4dM=; b=tSA1pI4Jl8S/n+vSlnQ+3QUOWLIv0bHHUqJRE2yA0qbN7qfWX9byAH1AS/wU+PJsHY fO9aZg+8AkIg6Io6bvLW/imxTG9Qu13E9w7iMTwvweDKIfq6l3AvuzYdjHNUUYr0FKce r/vMNPbwFc4XN//NHgKn+aWj1U4SGnAF67/4AKUXxVVqp3bLa03EWLuRI9MVjTrIRRLH PBCFppNPrkjbPhauso6OMNdmNh35DieNQh2TPgfQ/nGbgl9jHtIaX/7Zslm9bPa/ikID WdCwUg8WgKaYSQg6bRMPE2SXDoAom/l8ajZJ5KJFJOCPL1+aKIKNJCpSmHvTwhS4Z6Bf Q3bQ== X-Forwarded-Encrypted: i=1; AJvYcCX9rBjKOz5iEBnCGs80ZWq2A7q1Giib/IP0meRdfqHAPbIusTtYfMuLHvWUYlPR/MfrlzkJVDys8FBbUdT759VzQpv0bdUcrGIFPkZsdWh6wJNP X-Gm-Message-State: AOJu0YyJeLUz019BLo9D4fdNeJYDbonlDBOQKvWgyGHbUZfLQprF7R+o rRwHjo5zGts+bLsfnVtnZQ0HdmHFYZb8IAHFnrq/GMkECNmdepZI23pwhH3K5Q== X-Google-Smtp-Source: AGHT+IFmnzPxrt0NSgpqrcrcZRoqXcsn80MGQDUg9orMNp9a8Nf+5zRSEXAlLMIVzysgIpUYrSoqWg== X-Received: by 2002:a05:6830:1004:b0:6e6:9ac1:29ae with SMTP id a4-20020a056830100400b006e69ac129aemr871otp.16.1710776977099; Mon, 18 Mar 2024 08:49:37 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id h13-20020a9d600d000000b006e680de6fc4sm1043379otj.20.2024.03.18.08.49.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Mar 2024 08:49:36 -0700 (PDT) Date: Mon, 18 Mar 2024 08:49:34 -0700 From: Noah Misch To: Bertrand Drouvot Cc: Michael Paquier , PostgreSQL Hackers Subject: Re: Autogenerate some wait events code and documentation Message-ID: <20240318154934.10.nmisch@google.com> References: <69588eaf-02d7-95a8-0da4-3e120de16a59@gmail.com> <0b3cdac7-f078-61a6-76e0-99db7aae78ce@gmail.com> <20240317183114.16@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Mar 18, 2024 at 09:04:44AM +0000, Bertrand Drouvot wrote: > --- a/src/backend/utils/activity/wait_event_names.txt > +++ b/src/backend/utils/activity/wait_event_names.txt > @@ -24,7 +24,12 @@ > # SGML tables of wait events for inclusion in the documentation. > # > # When adding a new wait event, make sure it is placed in the appropriate > -# ClassName section. > +# ClassName section. If the wait event is backpatched to a version < 17 then > +# put it under a "Backpatch" delimiter at the end of the related ClassName > +# section. Back-patch from v17 to pre-v17 won't use this, because v16 has hand-maintained enums. It's back-patch v18->v17 or v22->v17 where this will come up. > +# Ensure that the wait events under the "Backpatch" delimiter are placed in the > +# same order as in the pre 17 wait_event_types.h (see VERSION_FILE_SYNC as an > +# example). I expect the normal practice will be to put the entry in its natural position in git master, then put it in the backpatch section for any other branch. In other words, the backpatch regions are always empty in git master, and the non-backpatch regions change in master only.