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.96) (envelope-from ) id 1wzazk-0046fj-2L for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2026 14:22:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wzazj-002O06-27 for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2026 14:22:19 +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.96) (envelope-from ) id 1wzVjS-000xnJ-18 for pgsql-docs@lists.postgresql.org; Thu, 27 Aug 2026 08:45:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wzVjP-00000001W90-13lB for pgsql-docs@lists.postgresql.org; Thu, 27 Aug 2026 08:45:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=aZdziu5YGuhw5H/soe5Vhjq7uGOKSblc7sAv69c6JSA=; b=2wUcJpEgHMNGI/TPjYcMyjfKME iM8zYB4m/zIknY7Czumw1kGVsNDkvnmilJUvhRymx6n9wAxJYb3i+7Myrbk75wNDwGmf2wPbVLA44 PHaPCJEheq7IJDxVhgnfDgtjlBaQpp+wTsJgE/cAL/X+eFXTOq50g60VQMnpO7HcdROBC2qWEjCFQ dflENCPU6lzhWWGE42gDCA7jT5qUYnIe+/9/C7ETli6yMQJp578NKqmz/DCQ5EW8bA8xalA9nMhrS +/jNmpnkTA2Vmk1tNO0PTD7En88xw7caMOte+mby/S3YmrD2jvtUV/YMyIcgpSCDIP8etE2hfE2hW c350cvJw==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wzVjO-0083L2-00 for pgsql-docs@lists.postgresql.org; Thu, 27 Aug 2026 08:45:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1wzVjM-00000004FcN-24C7 for pgsql-docs@lists.postgresql.org; Thu, 27 Aug 2026 08:45:04 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: 4.1.4. Special Characters To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: y.saburov@gmail.com Reply-To: y.saburov@gmail.com, pgsql-docs@lists.postgresql.org Date: Thu, 27 Aug 2026 08:44:29 +0000 Message-ID: <178782026936.2606573.10270614257871556098@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/sql-syntax-lexical.html Description: >> The asterisk (*) is used in some contexts to denote all the fields of a table row or composite value. As for Postgres specifically, you can add an example like `SELECT ctid, * FROM t;` and a link to Section 5.6, =E2=80=9CSystem Columns.=E2=80=9D