Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oziDk-0003H9-1U for pgsql-docs@arkaria.postgresql.org; Mon, 28 Nov 2022 17:47:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oziDh-0001qq-Uz for pgsql-docs@arkaria.postgresql.org; Mon, 28 Nov 2022 17:47:05 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oziDh-0001qg-Na for pgsql-docs@lists.postgresql.org; Mon, 28 Nov 2022 17:47:05 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oziDe-0001YF-SM for pgsql-docs@lists.postgresql.org; Mon, 28 Nov 2022 17:47:04 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2ASHl0x1635776; Mon, 28 Nov 2022 12:47:00 -0500 From: Tom Lane To: Kirk Wolak cc: Laurenz Albe , "David G. Johnston" , Bruce Momjian , ailjushkin@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: nextval parameter is not clear In-reply-to: References: <166608103231.2042183.13992576112735261253@wrigleys.postgresql.org> <21e017222199f3ca397fa70549140d226236e4b6.camel@cybertec.at> <0c0eddb287571e72a2df1be8758fbbb0cb7cc378.camel@cybertec.at> <45249! 3.1669614328@sss.pgh.pa.us> Comments: In-reply-to Kirk Wolak message dated "Mon, 28 Nov 2022 12:23:01 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <635774.1669657620.1@sss.pgh.pa.us> Date: Mon, 28 Nov 2022 12:47:00 -0500 Message-ID: <635775.1669657620@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Kirk Wolak writes: > my goal is to get an "approach" accepted, this is the first. Ultimately, I > would love to see > the documentation of functions with examples like this everywhere. I'm not for that. func.sgml is already massive, and doubling its size with extensive examples doesn't seem like an improvement. Admittedly, we probably don't need long examples for many of the functions, so maybe we wouldn't end up with quite that much bloat; but it still seems like the wrong approach. In my view, that chapter is more in the nature of reference material, so extended examples ought to go somewhere else. I could see adding a section about sequences and identity columns to chapter 3 in the tutorial. > Preferably where someone > can copy/paste the example and see the results. As far as that goes, there's already an idea that src/tutorial/ should contain SQL scripts that you can step-execute to follow along with the tutorial docs. This hasn't been followed through on very well --- chapter 2 is covered, but chapter 3 mostly not. No time like the present to make it better, though. If your ambition is to make self-contained working examples, making sure that they execute as a script is good discipline. regards, tom lane