I think if you want to go in that direction, you should refactor saying something like "* is the shorthand for all the user-defined columns (see system columns)". What do you think?
On Mon, Nov 2, 2026 at 4:55 AM Arvind Kandpal <[email protected]> wrote: > Hi Peter, > > Following up on the v2 patch I sent to the list on Oct 28, based on your > suggestion to update the SELECT reference page instead of section 4.1.4. > I'm attaching it again here for convenience. > > When you have time, could you take a look and let me know if it looks good > or needs any changes? > > Thanks and Regards, > > On Wed, Oct 28, 2026 at 3:43 PM Arvind Kandpal <[email protected]> > wrote: > >> Subject: Re: 4.1.4. Special Characters >> >> On 28.10.26 Peter Eisentraut wrote: >> > I think the section that you are patching is more for roughly mentioning >> > all the possible uses of various characters, but it's not the >> > authoritative source for what all those characters mean in detail in >> > those contexts. Otherwise, this could get out of hand. I would have >> > expected to find that for this particular case on the SELECT reference >> > page, but it's not mentioned there either. Maybe that page should be >> > updated? >> >> Thanks for the review. That makes sense. >> >> The attached v2 drops the change to section 4.1.4 and instead adds a >> sentence to the SELECT List section of the SELECT reference page. It >> says that neither * nor table_name.* includes system columns, which >> must be listed by name, and links to the System Columns section. >> >> The docs build cleanly with make check and make html. >> >> Thanks and Regards, >> >> >> On Wed, Oct 28, 2026 at 3:32 PM Peter Eisentraut <[email protected]> >> wrote: >> > >> > On 28.10.26 09:15, Arvind Kandpal wrote: >> > > The attached patch adds a sentence to the asterisk item in section >> > > 4.1.4, saying that system columns are not included in * and must be >> > > selected by name, with the suggested example and a link to the System >> > > Columns section. >> > > >> > > I built the docs locally (make check and make html) and the new text >> > > and link render fine. >> > >> > I think the section that you are patching is more for roughly mentioning >> > all the possible uses of various characters, but it's not the >> > authoritative source for what all those characters mean in detail in >> > those contexts. Otherwise, this could get out of hand. I would have >> > expected to find that for this particular case on the SELECT reference >> > page, but it's not mentioned there either. Maybe that page should be >> > updated? >> > >> >> >> -- >> Arvind Kandpal >> Junior Software Engineer >> (+91) 9650266413 <+91%2096502%2066413> www.ksolves.com >> >> Years of >> listing on >> > > > -- > [image: Arvind Kandpal] > Arvind Kandpal [image: LinkedIn] > <https://www.linkedin.com/in/arvind-kandpal-4635b1229/> > Junior Software Engineer > [image: Phone] (+91) 9650266413 <(+91)+9650266413> [image: Website] > www.ksolves.com > [image: Great Place to Work] [image: CMMI Level 3] [image: ISO] [image: > Salesforce Summit Partner] [image: Odoo Gold Partner] [image: Figma > Partner] > [image: Ksolves - AI First, Always] > [image: Celebrating] > [image: 6] Years of > listing on > [image: Indian Stock Exchange] > > >
