4.1.4. Special Characters
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, “System Columns.”
Hi,
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.
Thanks & Regards,
On Wed, Oct 28, 2026 at 1:40 PM PG Doc comments form
<noreply@postgresql.org> wrote:
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, “System Columns.”
--
Arvind Kandpal
Junior Software Engineer
(+91) 9650266413 www.ksolves.com
Years of
listing on
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?
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 <peter@eisentraut.org> 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 www.ksolves.com
Years of
listing on
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 <arvind.kandpal@ksolves.com>
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 <peter@eisentraut.org>
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.comYears 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]
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 <arvind.kandpal@ksolves.com>
wrote:
Show quoted text
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 <arvind.kandpal@ksolves.com>
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 <peter@eisentraut.org>
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.comYears 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]
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?
Thanks for the suggestion. Changing the existing sentence is cleaner
than adding a new one.
The attached v3 changes the first sentence of that paragraph on the
SELECT reference page to say that * is a shorthand for all the columns
of the selected rows, not including system columns, with a link to the
System Columns section. I used "not including system columns" instead
of "user-defined columns", since the docs don't use that term for this.
I also dropped the example to keep the change small.
The docs build cleanly with make check and make html.
Thanks & Regards
On Tue, Nov 3, 2026 at 9:06 AM Matemática A3K <matematica.a3k@gmail.com> wrote:
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 <arvind.kandpal@ksolves.com> 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 <arvind.kandpal@ksolves.com> 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 <peter@eisentraut.org> 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 www.ksolves.comYears of
listing on--
Arvind Kandpal
Junior Software Engineer
(+91) 9650266413 www.ksolves.comYears of
listing on
--
Arvind Kandpal
Junior Software Engineer
(+91) 9650266413 www.ksolves.com
Years of
listing on
On Tue, Nov 3, 2026 at 4:37 AM Arvind Kandpal
<arvind.kandpal@ksolves.com> wrote:
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?Thanks for the suggestion. Changing the existing sentence is cleaner
than adding a new one.The attached v3 changes the first sentence of that paragraph on the
SELECT reference page to say that * is a shorthand for all the columns
of the selected rows, not including system columns, with a link to the
System Columns section. I used "not including system columns" instead
of "user-defined columns", since the docs don't use that term for this.
I also dropped the example to keep the change small.
Hey Arvind, it LGTM with a small change: "* is a shorthand for all the
columns of the selected rows (not including <xref
linkend="ddl-system-columns" endterm="system columns"/>)." What do you
think?
Hey Arvind, it LGTM with a small change: "* is a shorthand for all the
columns of the selected rows (not including <xref
linkend="ddl-system-columns" endterm="system columns"/>)." What do you
think?
Thanks for the review. I like that wording better.
endterm needs the id of an element, not free text, so this form fails
the doc check. I used <link linkend="ddl-system-columns">system
columns</link> instead, which gives the same rendered text, with
"system columns" as the link.
The attached v4 has this change. The docs build cleanly with make
check and make html.
I have also added the patch to the commitfest:
https://commitfest.postgresql.org/patch/7599/
Thanks,
Arvind Kandpal
On Wed, Nov 4, 2026 at 8:18 PM Matemática A3K <matematica.a3k@gmail.com> wrote:
On Tue, Nov 3, 2026 at 4:37 AM Arvind Kandpal
<arvind.kandpal@ksolves.com> wrote: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?Thanks for the suggestion. Changing the existing sentence is cleaner
than adding a new one.The attached v3 changes the first sentence of that paragraph on the
SELECT reference page to say that * is a shorthand for all the columns
of the selected rows, not including system columns, with a link to the
System Columns section. I used "not including system columns" instead
of "user-defined columns", since the docs don't use that term for this.
I also dropped the example to keep the change small.Hey Arvind, it LGTM with a small change: "* is a shorthand for all the
columns of the selected rows (not including <xref
linkend="ddl-system-columns" endterm="system columns"/>)." What do you
think?
--
Arvind Kandpal
Junior Software Engineer
(+91) 9650266413 www.ksolves.com
Years of
listing on