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 1v32hC-00AR4s-Ar for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Sep 2025 01:28:54 +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 1v32h9-00G8uN-4Y for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Sep 2025 01:28:51 +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 1v32h8-00G8uF-PJ for pgsql-hackers@lists.postgresql.org; Mon, 29 Sep 2025 01:28:51 +0000 Received: from mail-oa1-x36.google.com ([2001:4860:4864:20::36]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v32h7-000cz1-1D for pgsql-hackers@postgresql.org; Mon, 29 Sep 2025 01:28:51 +0000 Received: by mail-oa1-x36.google.com with SMTP id 586e51a60fabf-35ba7c71bfdso2841642fac.3 for ; Sun, 28 Sep 2025 18:28:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1759109327; x=1759714127; darn=postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KnZBiP8YsQMds5dMhndWJTdXfn5ft4YJBSGcD/MkQhE=; b=VhvWNONlwQqvXvMv7V3QscpkD02ERbLQekNsSV5kSfyTRMUrQoGdrKotCQ8PV0lA09 iNNuS58BJGgLIjhM4rSTPt3fUyl8EmMYyxB/u2N0MVEpMjhJDPOFjlhaS0/krFFfPNO4 FFa1tklbK4zVru8QcblN9nGFsT9fCz0sqF2h69RRRMlzGd6+yYPZvLRC//dawZuQy4Gq Z/kA8Q+WbXx+CuPElWvvsqeAu7CMmAdq4v+fST7kw2l4ssC8PQMGLOcAqFwEtRBjB+c1 MAsU8gF4t69NGNgBvtIP5l/Kp5you0J96emAZVFP5L9qc9tpKNbvb6XUsTbvKxRY3iWk 1YuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1759109327; x=1759714127; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KnZBiP8YsQMds5dMhndWJTdXfn5ft4YJBSGcD/MkQhE=; b=BRlhHnoYfSPjt8z5tORNbh52JD0zamCimXXCk37biZKgU3VcchT76Ocs52j+/ucroj XveiQiWQTDq2F1Qh9DAs7Q3VXBsM0hACTZp9f6wyMGxwFd9qrag1UIEysDsgC4zRIlDL oUu1GtBc6nPshyWmTEZ+EGSlz1+A9HwOH+9T7gm0R/kpPmRJVV8cKTmAH/rJj7ufBTXL //Th2g5uE/zsu5HItywbUMHcRgJEA/4p0RCRJpnOGF50mCVGfv1lwJV1ZcgA9mR+zxPP 1f0ovon6n0BzwKgSmrxSG2qoD89UWidJXD2kJ0mbImwzDBnWbrXAnZXbm30nhOB7sFdI oDSw== X-Gm-Message-State: AOJu0Yya3zGxqxd1tOFX7l1F5rPWWb3d3YtOAUNPI6d2GUclA883nBiC 9Nlucnefurp77n//si97JOEcFt3kJOeNCnKZd8VAOAo6opHDehxkJIxewEce7esrOLKuIn7KguU Sdj/9SsJq8R7xFXIe4XvL/xxp67TxNas= X-Gm-Gg: ASbGncvfIcXiRCW8CIjqhOycvJFAy3RRdTj67U1JkrywlPR+dNeTJfAu7uhshZ0N4a5 b2OAsHfzuof+Du6mWoITkk/Vqn1C37qkRJX6GdfoP7yXpEoa+gc3gryQzDR90u2IH4jKU5EWDbT ALwbCkBMYcOGlSwUiBl2KCHT2IBS6ppzWnErDjwmmAiCNPYL1MYTl/UnySv5n8nnVmfLmH1ucum 4trdxOm8Dh40XgJ0LE8T/lseexTQNj7GdD2n3ERZhHPXEKuimM= X-Google-Smtp-Source: AGHT+IGOkWlvtBxzLPsvwog7cT//PRFUs5D6hELD4xs5lqw0FU6LzTQNPtkZTEKRO4RwpSUinEznbkcIcaJggMYt9Vc= X-Received: by 2002:a05:6870:c6a5:b0:315:c0bc:4bb6 with SMTP id 586e51a60fabf-35ebee23f8amr7646302fac.5.1759109326736; Sun, 28 Sep 2025 18:28:46 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6802:5402:b0:5f3:5bf6:6b0b with HTTP; Sun, 28 Sep 2025 18:28:45 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Sun, 28 Sep 2025 20:28:45 -0500 X-Gm-Features: AS18NWAvMKK8x4oO7U_4335YVE17apTqP8vOGj_bUehBhOXnIBE8kER2VRXr_uM Message-ID: Subject: Re: create table like including storage parameter To: jian he Cc: PostgreSQL-development Content-Type: multipart/alternative; boundary="0000000000008a95cf063fe68ee2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008a95cf063fe68ee2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sunday, September 28, 2025, jian he wrote: > > Since we already support INCLUDING STORAGE, I=E2=80=99m not sure that > INCLUDING STORAGE PARAMETER is the right syntax to go with. > I=E2=80=99d just call it =E2=80=9Cincluding parameters=E2=80=9D; sure, all = of the existing ones are storage related, but if there were non-storage ones we=E2=80=99d include th= ose as well, so qualifying with a parameter type doesn=E2=80=99t seem correct. David J. --0000000000008a95cf063fe68ee2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sunday, September 28, 2025, jian he <jian.universality@gmail.com> wrote:
Since we already support INCLUDING STORAGE, I=E2=80=99m not sure that
INCLUDING STORAGE PARAMETER is the right syntax to go with.

I=E2=80=99d just call it =E2=80=9Cincludin= g parameters=E2=80=9D; sure, all of the existing ones are storage related, = but if there were non-storage ones we=E2=80=99d include those as well, so q= ualifying with a parameter type doesn=E2=80=99t seem correct.
David J.
--0000000000008a95cf063fe68ee2--