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 1uj2f5-002202-Nh for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Aug 2025 21:24:04 +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 1uj2f4-005P9U-4u for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Aug 2025 21:24:02 +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 1uj2f3-005P9M-Np for pgsql-hackers@lists.postgresql.org; Mon, 04 Aug 2025 21:24:01 +0000 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uj2f1-000lOz-10 for pgsql-hackers@lists.postgresql.org; Mon, 04 Aug 2025 21:24:01 +0000 Received: by mail-io1-xd33.google.com with SMTP id ca18e2360f4ac-881833b7adbso90692839f.1 for ; Mon, 04 Aug 2025 14:23:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1754342637; x=1754947437; darn=lists.postgresql.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=1HH/5vxZozB41ae4MJKr3B/1XOOtBxtYcAm/rDMbHco=; b=RE5nqT/Pt8lazAYyYoaZ3x7RtaI+I1/VwM1gJx9M2+9hNs/UffXaMeHo5JPgae3wJP xGGyiWITzhITgxfghHZKKz/lMkMZ1OIzCwtZ4ZGWepBmVcgjMWaSJX9GgfCMPg51HYl0 X/psod2Bo/gin+Jr3FBwYMRpIsdfE7mHaSKmV+28TQ39CvHutD32DODhaM0t3SrS8anP EoGV6bvkjrgQImkc+NQmU7Hhs/5Zn+Z2mSfBL1WArJR0+1576++cew6L7uamypcKwFSY 1Hs1AZ1xD1FG1xxEmRvrbweGNBEiq/NTa0A7bQixAT4zDPdVl8mSpJiE81E6aq034Ks3 gHwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754342637; x=1754947437; h=in-reply-to:content-transfer-encoding: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=1HH/5vxZozB41ae4MJKr3B/1XOOtBxtYcAm/rDMbHco=; b=VTgZqOos5q/tOmsii0a+l5p3EP/9cIdky7mUKQDgoHi1xHvF0ZkgUvlKX9i6OvKezN WzZd2C43kl2IvR2y0Z7qT/i5I+rP1lqF78msjL+4mzd8MLBJalLVwSLCoWLglRtTXYOX Z0Zw8AWcdYm6K4C1EcrxxkWyXnQmz5cae/plSs9IUDyynI8PFJlAlB+HZztaTqV7AAu7 91y7ze4YXio6NCcsx532Rw8ZIQUm4QKvfaBxfen2irLi/JAUBggtCjmjTk6zsYlxmdL0 FQ/pIO4N4lCFxV1t7K7MpGZ0iPKg8Rk2WMCdvA3xbaXNkDDAjmjir5+K5WqRkzR1XJOv nkjA== X-Forwarded-Encrypted: i=1; AJvYcCU7yZKPaR06hGPtJQOh6UGvCO3BUoJu7TZf5tivObWk8LjhAXAjqkl/3C5ti6G5KICzq7zMyzDOAS3v7dGf@lists.postgresql.org X-Gm-Message-State: AOJu0YzaXHlUstR51FXFRjMZ3d3WpZygjrhk03vmvQYubUUMksM+zzSJ vgYfndBxqqF5Gh2f6An7xgzIIsPmnr2wFHUcukbX+8cTMpMN172eUU2N X-Gm-Gg: ASbGncuLJ0QL9hEp1cMHbjc0Q1XiiIPsBx9GeRLGukKBisnWj8fiNrfp2A4IJjAvL1u Iz38HaZTR1jjMcxwu7kcKw/m9+T5lXhG3EN9oziDtSxLx3ZyTziDJ5kuL1gvMHTQUbOe7seos0V TWqogE/lSkzDXF8uUF0O0gnUhPoNSE2+fKLhESZt3Ro82M/2Bl+7ss4T+PDOgRwgFWP0Pki4SuT ke7ZrrHumeqhI5dmaGejGQv6+zTz+HT/5RFFSOM5mSrVYLg8xIDRPReilZL09dsiamw+cN3DDX3 w0L4Dw3vOWUHOWQUA39DVDjpj1AiJw4hcov3/JWNsBmESD8GMR1jXyes/k4MukZL6lLXye+n1LS lb8r+fbkpJMxofMUyflEflidqBcNl5B9VpO1W+PRM0ywQRygXO5ketaanVQRDY1CNpX+Q+lxmQd Ob/b1PywjAoTQ7jiqkb6yR5kE= X-Google-Smtp-Source: AGHT+IE9KiESN0Scd/bc/dCvkg99h61dMsGwXMK2d6rSweIwBPoi/iRj6sx6aauF+GvXVktjImhxmQ== X-Received: by 2002:a05:6602:7194:b0:87c:1a21:4d17 with SMTP id ca18e2360f4ac-8816831dec9mr1700236739f.1.1754342637247; Mon, 04 Aug 2025 14:23:57 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-50aa64aa203sm746763173.112.2025.08.04.14.23.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Aug 2025 14:23:56 -0700 (PDT) Date: Mon, 4 Aug 2025 16:23:55 -0500 From: Nathan Bossart To: Jacob Champion Cc: =?iso-8859-1?Q?=C1lvaro?= Herrera , Dave Cramer , PostgreSQL Hackers Subject: Re: More protocol.h replacements this time into walsender.c Message-ID: References: <202508041231.myxuzx2udlze@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Aug 04, 2025 at 02:11:26PM -0700, Jacob Champion wrote: > On Mon, Aug 4, 2025 at 12:56 PM Nathan Bossart wrote: >> The replication protocol uses many of the >> existing PqMsg macros already, so it would be a little strange if only a >> subset of the replication protocol messages used the special prefix. > > May I ask why? These messages are legitimately different; they're > tunneled through CopyData, so their reservations don't collide with > the top-level codes. Ah, I missed that finer detail. IIUC the codes at hands are _only_ used in these tunneled messages, in which case they belong to a distinct category. >> There's also backups, which use the replication protocol but >> have their own special characters [0]. If we're going the prefix route, >> would we add another prefix for those, or use the replication one? > > My vote would be to add another. 'p' is a password message in the > top-level protocol (one of many, actually), a progress message in a > backup stream, and a status request in a replication stream, so I > think they deserve their own namespaces. These also seem to use the same tunneling mechanism. I retract my objection. -- nathan