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 1qT84U-008VdP-2T for pgsql-hackers@arkaria.postgresql.org; Mon, 07 Aug 2023 21:47:26 +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 1qT84R-00Bq8k-Tp for pgsql-hackers@arkaria.postgresql.org; Mon, 07 Aug 2023 21:47:24 +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 1qT84R-00Bq6a-I2 for pgsql-hackers@lists.postgresql.org; Mon, 07 Aug 2023 21:47:24 +0000 Received: from mail-pl1-x629.google.com ([2607:f8b0:4864:20::629]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qT84O-001AST-OO for pgsql-hackers@lists.postgresql.org; Mon, 07 Aug 2023 21:47:22 +0000 Received: by mail-pl1-x629.google.com with SMTP id d9443c01a7336-1bb7b8390e8so31698015ad.2 for ; Mon, 07 Aug 2023 14:47:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691444839; x=1692049639; 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=PWAWVZSTB0jDTm6WetwVhiiv5wR0s0dbgM7pUSRvkZE=; b=C4ZSFb7NADC+MZ9jYUPhL3uWFv8EVqQom4/xn8oTeuvxTIMVfgjeRWELLubi7vkGWt XLth8tlI2DBE3Xak4mWjawbf89PgX9XhPAG7ljxjZ9nGvDpQkqLoaZXX81vRlgaS24kn cJYvTgr5L4uc+CHhQAsnDUM2T+aewFiodRFxrEvLfpXkaWRYCpG1bbe5VHuK6DJc0Sjm W9n87UlZVmn9JZ9AhdvJYua3sBGdaT6cnQ7We5F9EsKaCwtT/sHKcpeTdYlu41ebHw3F gQ52ppglgjaDHjsJUEkNe1V5X+immdQOr1EJ9vWhdKf9aKvo42q9gVruiNg1YHFgizys Xxmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691444839; x=1692049639; 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=PWAWVZSTB0jDTm6WetwVhiiv5wR0s0dbgM7pUSRvkZE=; b=HS0Vlv4BYbHbBZVU9JuiVcZIBzzB/xUdJtj0Sn19SgqHUDI4R0mlA6tSpfOmcAlWIV zZKNDl/gSPu8Q2XfVx0H1YXKTVMABrhdIhUBxF3nvS/corZ9zEXoGtTNlnkfW13/w37+ 20u/z1W9Xf48yQsZY8ddlJ8UErjmINroptuDm+yc3i4H1CITqCijDxPlTUJIOf0xM43b yNOzZzkoPcrUMRpQs0p8y9/I6Y8Mg2opEIsqbM5MhMpkn9cdTi0Jmsxf1ki/3kTGox0s z9u0qTiV7eHc4a+/Xv0c8zQ84jtWwMAN8vkMwsp/ZJpsbWvJ1mmbfpKdWfEPX9gIXbzY kbfg== X-Gm-Message-State: AOJu0YwwNNUMfRAL6gdWFnZ9DICOBXaPdcQnpUSSdrV58V6X7hPegJHc QANyeQTxm8+9E01Y12G+3mE= X-Google-Smtp-Source: AGHT+IFPJuc5v812+pX+in6WP3zvOxTc1eFgJBMtPsco7fzLuhvPRX7xWCwOGeV3fOP8PSgbVFmELw== X-Received: by 2002:a17:902:82c5:b0:1b8:6cae:4400 with SMTP id u5-20020a17090282c500b001b86cae4400mr8272272plz.37.1691444838627; Mon, 07 Aug 2023 14:47:18 -0700 (PDT) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id l4-20020a170903244400b001b89891bfc4sm7344832pls.199.2023.08.07.14.47.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 07 Aug 2023 14:47:17 -0700 (PDT) Date: Mon, 7 Aug 2023 14:47:14 -0700 From: Nathan Bossart To: Tom Lane Cc: Dave Cramer , Robert Haas , Alvaro Herrera , Peter Smith , Tatsuo Ishii , pgsql-hackers@lists.postgresql.org Subject: Re: Using defines for protocol characters Message-ID: <20230807214714.GA1284531@nathanxps13> References: <20230807091044.jjgsl2rgheazaung@alvherre.pgsql> <838284.1691432698@sss.pgh.pa.us> <859245.1691438528@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <859245.1691438528@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Aug 07, 2023 at 04:02:08PM -0400, Tom Lane wrote: > Dave Cramer writes: >> On Mon, 7 Aug 2023 at 12:59, Robert Haas wrote: >>> PqMsgEmptyQueryResponse or something like that seems better, if we >>> want to keep the current capitalization. I'm not a huge fan of the way >>> we vary our capitalization conventions so much all over the code base, >>> but I think we would at least do well to keep it consistent from one >>> end of a certain identifier to the other. > >> I don't have a strong preference, but before I make the changes I'd like to >> get consensus. >> Can we vote or whatever it takes to decide on a naming pattern that is >> acceptable ? > > I'm good with Robert's proposal above. +1 -- Nathan Bossart Amazon Web Services: https://aws.amazon.com