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 1sRFHn-00E52N-Ea for pgsql-committers@arkaria.postgresql.org; Tue, 09 Jul 2024 18:09:55 +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 1sRFHl-00GsnL-ML for pgsql-committers@arkaria.postgresql.org; Tue, 09 Jul 2024 18:09:53 +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 1sRFHl-00GsnD-ET for pgsql-committers@lists.postgresql.org; Tue, 09 Jul 2024 18:09:53 +0000 Received: from mail-ed1-x533.google.com ([2a00:1450:4864:20::533]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sRFHi-001FCI-T2 for pgsql-committers@lists.postgresql.org; Tue, 09 Jul 2024 18:09:52 +0000 Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-58c947a6692so6795094a12.0 for ; Tue, 09 Jul 2024 11:09:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720548589; x=1721153389; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4+TKbeWjdW49wg1aKKNwecQ8mol+bATSHy1/yUEHZJY=; b=RaS1IvEfVzgqZe63mk8saUFShBr1EPfdtWtYvdd2FDXb0RW4jRwd7w+neCBmux8WKy uoazlakg+KusgC+NK/+1PJOWWyZrc0VEIe0B992nYEvuEttAJ8nvPPpsD5p7bwpDB7La bAqbQhNppOsj3/m1NPLBOoFIz8DDvzbkZy7Xz1jvpgGy2duCTGOHSzMka3xBeuvxiQCq P6me29IZ/pDrR+1tYUno81FyGW9lEyE22mZZf+luQI8f7kaqggRJjAd6BUVKO6R9PRZ+ 8AihiR30bnjFZN20hpl9pWAm463qm5K52YHM9QOYfVp/ah6s9bk1t8QF3ZX9wCz60J0q PvBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720548589; x=1721153389; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4+TKbeWjdW49wg1aKKNwecQ8mol+bATSHy1/yUEHZJY=; b=GU4UppTI3ejr1wtVPnK7BC3EzOGmb3VchQ1vne2ZFbSsa41fiaLn1PGVcInUQ7DyZe kSVswxr06q57Tx8ti3dOIXdSnA7Z3iN/OgF/66rZ8rEkRjNY4FBu44LVlXTtIKVQuaUi lPKemQuY/XBXdbn/LDbDaQ3l7vOCDJGpc+Stb28pMoZprhhdIQrpyl3ez5YUlHMhVFqt 8pp1UJjxCQfcaNhMWa1yJanEe89E0377j3UWx7KKKW6pE3WSsUrjo1NANatbqtRkSxrJ dPG6z0nYqqHWABSjI/bhrsHUym7j/RwvS9VXag0pjasspfNSA/rV5aAXP6s941GRT/wW of0g== X-Gm-Message-State: AOJu0YxllTmUl5eTY55dVVINtPvszdwEV6nchGJL7DrsLZtimOVMnKY9 4FgqjGaCc9b+ma04wSgN8tCnE/L5lkll2gJnrbn74vyr5GG835XAlgqCwm8aOwPViVbf58NLn/y ph0jc5zj1l/TgBUyioNnoHV/a8fk= X-Google-Smtp-Source: AGHT+IGVACYFg+SF7H1g9f45vK8AT1o0F0wyHUdH6kreCBvFyERVs1WBknlJLWmmxL6ib0KLlde4/WRLy2BR/kp/PhI= X-Received: by 2002:a17:906:71ca:b0:a77:f1c8:7cb7 with SMTP id a640c23a62f3a-a780b89f39dmr203430166b.73.1720548589022; Tue, 09 Jul 2024 11:09:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Thomas Munro Date: Wed, 10 Jul 2024 06:10:09 +1200 Message-ID: Subject: Re: pgsql: Replace BackendIds with 0-based ProcNumbers To: Heikki Linnakangas Cc: pgsql-committers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --- a/src/backend/libpq/pqmq.c +++ b/src/backend/libpq/pqmq.c @@ -26,7 +26,7 @@ static shm_mq_handle *pq_mq_handle; static bool pq_mq_busy = false; static pid_t pq_mq_parallel_leader_pid = 0; -static pid_t pq_mq_parallel_leader_backend_id = InvalidBackendId; +static pid_t pq_mq_parallel_leader_proc_number = INVALID_PROC_NUMBER; I guess it was a historical mistake that this variable of type pid_t instead of BackendId, but now it should be ProcNumber?