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 1wYrdU-000Zkg-2B for pgsql-docs@arkaria.postgresql.org; Sun, 14 Jun 2026 20:40:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wYrdQ-008sA1-2z for pgsql-docs@arkaria.postgresql.org; Sun, 14 Jun 2026 20:40:48 +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 1wYrdQ-008s9s-2F for pgsql-docs@lists.postgresql.org; Sun, 14 Jun 2026 20:40:48 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wYrdM-00000000PFt-1xjc for pgsql-docs@lists.postgresql.org; Sun, 14 Jun 2026 20:40:48 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 65EKeYGn118333; Sun, 14 Jun 2026 16:40:34 -0400 From: Tom Lane To: Laurenz Albe cc: jochen.bandhauer@gmx.net, pgsql-docs@lists.postgresql.org Subject: Re: 7.2.1. The FROM Clause In-reply-to: <36df7ebde5717e34d88228266c8aef21dc6e8c75.camel@cybertec.at> References: <178125831604.1285960.8250607197280951685@wrigleys.postgresql.org> <36df7ebde5717e34d88228266c8aef21dc6e8c75.camel@cybertec.at> Comments: In-reply-to Laurenz Albe message dated "Sun, 14 Jun 2026 22:09:34 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <118331.1781469634.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 14 Jun 2026 16:40:34 -0400 Message-ID: <118332.1781469634@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Laurenz Albe writes: > But I understand your confusion. To be honest, I only learned about the= syntax > "tab *" a few days ago. Digging through the history, this syntax has be= en > obsolete since 2000. I think we could remove both the paragraph that co= nfuses > you and the asterisk from the syntax diagram. We can leave the obsolete > syntax to accomodate SQL code that hasn't changed for over 25 years, but= I don't > see a reason to keep it in the documentation. I think we've discussed that before, and concluded that removing the docs would be a disservice to users who are trying to read old code that does this and don't know what it means. Maybe that argument is too weak now to justify keeping the docs, but I'm unsure. I'd be inclined to just rephrase this sentence in hopes of making it less ambiguous. regards, tom lane