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 1v1w3T-00EP8j-Hv for pgsql-docs@arkaria.postgresql.org; Fri, 26 Sep 2025 00:11:19 +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 1v1w3R-006sum-U1 for pgsql-docs@arkaria.postgresql.org; Fri, 26 Sep 2025 00:11:17 +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 1v1w3R-006sue-MT for pgsql-docs@lists.postgresql.org; Fri, 26 Sep 2025 00:11:17 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v1w3O-00074c-1m for pgsql-docs@lists.postgresql.org; Fri, 26 Sep 2025 00:11:17 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-3544c64380eso2244236fac.3 for ; Thu, 25 Sep 2025 17:11:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1758845472; x=1759450272; darn=lists.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=sADapKFixtDw5tkS3DK3sjesj12DO4U0SrFzz72GfAg=; b=gtIy+WbcqJcFSd0uzmuVAT5VT54GRr77t1VPw1h+zMNwHlPRzLV+PIemtcjVur0OIv dGTbtbI6jgAiKxwzz3HOLgC50tS9t/STe8iLdRIEqOcXoBf9sC2t8bC1nf8hOhyfBKfZ U6BCnH6gD2s3O1MziW/p4q79RkFv+R56+WDvlxt+AwW/EpZTheol39yAANf1rqUeOcMm q4hMhOlZqp9qfXr1ZC/wBcKDpkCibnGbkv8/F+mOSLuHal3OsqStRXNGiG4a3QRUVohn qD7OgTlquefQrxbxnep1n4TJP7qFqbtCrVQvquV88ttXc8ROSB3rnKh2oLGphxFMvIfH UqSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1758845472; x=1759450272; 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=sADapKFixtDw5tkS3DK3sjesj12DO4U0SrFzz72GfAg=; b=kyFk63AIr1kkCQn/zFGmw6mzhojKtN0xXnH1Fy/EqS9bxVI+VOwsaez+y2k1TFe+aT BSGhU7nZOKvMUPqEkd+M1oqkkr6T31SqQOOG2viy4VcLq4IwgO+c+1ACyFlVp89Plx2M iaVL/Kl3lAISmFwFIdr7krxcH5GAfBojkPm416O2dNCGZ8bNiWO/6Ipd46mXUrZUhB8D kGTiZT3k/oC6EqmEyaTusB4RpKSZPuooJEreyjGrTd5HK1thKlx5QFNn85YIAM6ajbtZ iscKbDR66P20QYo4oQuw/PHtRUBsqVJhTsw1CjWkVtaiVAeRyWJtt5y1/pY5EqKivoe0 xrLA== X-Gm-Message-State: AOJu0YygXIAXDjdyd9uW32ylZQvOBHLYs1tsIdyzJBEDFuAhX1uI3hoo 1E4ARpEE0EGnMUk2gUR4zTH49PaklF/Wehc7qcNpjIdBJZlrIfgWboIX/5ekACuvbvwrLZIhBNb 40LQB3978zy46yxgpjf6jyXYo9KUZWmU= X-Gm-Gg: ASbGncuUM9Rzx3e4H9vdctHfGQT5TQA6OMoBbxIiX6sv/gw37L+8JZ4dYEyd7MivX0S sV4JymCBcRPpO607Gn9bCqOi0xr30AlgFRmF5ebe9KHF8YUjQUv+U3MPFtBLWl6v38XogSSryzS bAFqPPXC51MQp1eVhusC96VBlgkzfQSS3kQPLWeA6LAUf29E02ZWaK5qgnBUA/Hg8papubA0ZBA wdCmA== X-Google-Smtp-Source: AGHT+IF0fD/EsvNyPA+oMa55ffpIuKl9J95QblZh5t5sratlvYzF/FwAb50wih18sYjHPHXxL7ljyfeP7NCEiKSY0+Q= X-Received: by 2002:a05:6871:4f10:b0:36c:abe0:83e5 with SMTP id 586e51a60fabf-36cabff1af4mr277436fac.17.1758845472288; Thu, 25 Sep 2025 17:11:12 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6802:361b:b0:5f3:5bf6:6b0b with HTTP; Thu, 25 Sep 2025 17:11:11 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Thu, 25 Sep 2025 18:11:11 -0600 X-Gm-Features: AS18NWAtXJ4k6q0Vib2O2nRHjkCtsv88Bo83eN907hiFbzaBDbOXiU3yUzzi0Qc Message-ID: Subject: Re: make create_table.sgml Synopsis section less wide To: jian he Cc: "pgsql-docs@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000009733cd063fa91f7c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009733cd063fa91f7c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thursday, September 25, 2025, jian he wrote: > hi. > > https://www.postgresql.org/docs/devel/sql-createtable.html > Synopsis section, > The second line is currently too long, and the explanation for > exclude_element > (the third line from the bottom) is also quite wide (lengthy), the > like_option also too long. > > I mentioned this earlier, and while working on CREATE TABLE LIKE related > features, I came across this minor issue again. > > If we make it less wide, then we don't need to scroll horizontally. > please check the attached screenshot to see the effect of the change > > what do you think? > I=E2=80=99m not able to give this much attention myself at the moment, henc= e it being in drafts, but here is where this topic presently stands. https://www.postgresql.org/message-id/flat/CAKFQuwYfMV-2SdrP-umr5SVNSqTn378= BUvHsebetp5%3DDhT494w%40mail.gmail.com https://commitfest.postgresql.org/patch/5547/ David J. --0000000000009733cd063fa91f7c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thursday, September 25, 2025, jian he <jian.universality@gmail.com> wrote:
hi.

https://www.postgresql.org/docs/devel/sql-createtable.html
Synopsis section,
The second line is currently too long, and the explanation for exclude_elem= ent
(the third line from the bottom) is also quite wide (lengthy),=C2=A0 the like_option also too long.

I mentioned this earlier, and while working on CREATE TABLE LIKE related features, I came across this minor issue again.

If we make it less wide, then we don't need to scroll horizontally.
please check the attached screenshot to see the effect of the change

what do you think?

I=E2=80=99m not able to give this much att= ention myself at the moment, hence it being in drafts, but here is where th= is topic presently stands.


David J.

--0000000000009733cd063fa91f7c--