From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
cc: Kirk Wolak <wolakk@gmail.com>,
        "David G. Johnston" <david.g.johnston@gmail.com>,
        Bruce Momjian <bruce@momjian.us>, ailjushkin@gmail.com,
        pgsql-docs@lists.postgresql.org
Subject: Re: nextval parameter is not clear
In-reply-to: <f7a51be79a5146740954e0b9b70515529a1d944b.camel@cybertec.at>
References: 
 <166608103231.2042183.13992576112735261253@wrigleys.postgresql.org>
 <Y30ekxQpiIaG9eSl@momjian.us>
 <CACLU5mQBVn+cyeAAbs7O6c8h14MBurhuxpp7z+TXWo2+vQcO+w@mail.gmail.com>
 <CAKFQuwau7CpY+TLufpU1RPPzyLzjS0mvrXnSLf+eGSUJS-_pRQ@mail.gmail.com>
 <CACLU5mQ1LTz9BnG-bbfCmwzytyUFwej90XBnFtQJKQkubS9Khw@mail.gmail.com>
 <CACLU5mTKsNgWfY9qcsn1fhMRXbfJ0M8bPEwgXbmanxVgdKPQ7A@mail.gmail.com>
 <CACLU5mS4b3xM-tuMpT2oP-pqwwnHJbSeLDBzZSs9Lq_ObgMu7Q@mail.gmail.com>
 <21e017222199f3ca397fa70549140d226236e4b6.camel@cybertec.at>
 <CACLU5mShHGjroH=Cp_k6i-T+357_Fhxahc5NqpNPoJnN56GyFg@mail.gmail.com>
 <CAKFQuwarCJs9bbgJ9_PtsCBJKmSM1UnLx80J5JUJm1eJyYzHXQ@mail.gmail.com>
 <CACLU5mRn-xHKP9irkBQvYCQYKNDCcud66zJHHaHNHoOMA4kmVQ@mail.gmail.com>
 <0c0eddb287571e72a2df1be8758fbbb0cb7cc378.camel@cybertec.at>
 <CAKFQuwYuu_FrZZ=TEdUPdB4c-hbsCHSKD+XSUdDFrGnaDMQ_=A@mail.gmail.com>
 <CACLU5mTmEieU-uTF6bNm9T5Y94gd1g_cgz_JDLz6Qw36RjcBHQ@mail.gmail.com>
 <CACLU5mR7JsrJN6qnz=Gh4Ta-0E1hsL++DLLMeWDMQMCVKbOQvw@mail.gmail.com!
 > <f7a51be79a5146740954e0b9b70515529a1d944b.camel@cybertec.at>
Comments: In-reply-to Laurenz Albe <laurenz.albe@cybertec.at>
	message dated "Mon, 28 Nov 2022 04:34:56 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <452492.1669614328.1@sss.pgh.pa.us>
Date: Mon, 28 Nov 2022 00:45:28 -0500
Message-ID: <452493.1669614328@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/452493.1669614328%40sss.pgh.pa.us>
Precedence: bulk

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> Now I think that is taking it too far.  Your code sample would be great
> for a tutorial, but it is too elaborate for the technical documentation.
> The example should focus on the sequence functions, but more than half
> of the code describes other parts of PostgreSQL:

Yeah, that stuff seems quite out of place here.

> I am alright with having a CREATE TABLE with a DEFAULT and an INSERT or two;
> whatever it takes to show the functions in a realistic scenario.
> For example, you could INSERT a row that overrides the DEFAULT, then call
> "setval()" to readjust the sequence.

I don't believe we have such detail around very many, if indeed any,
of our other functions' documentation.

			regards, tom lane