Re: DOCS - Add introductory paragraph to Getting Started chapter
Hi,
Following up on Tom's suggestion that Chapters 2 and 3 of the
tutorial likewise lack introductory paragraphs, I've attached a
patch that adds them.
Chapter 2 (The SQL Language) gets a paragraph summarizing tables,
queries, joins, aggregates, and data modification.
Chapter 3 (Advanced Features) gets a paragraph summarizing views,
foreign keys, transactions, window functions, and inheritance.
Regards,
Dapeng Wang
Attachments:
0001-doc-add-introductory-paragraphs-to-tutorial-Chapters.patchapplication/octet-stream; name=0001-doc-add-introductory-paragraphs-to-tutorial-Chapters.patchDownload+15-1
On 4/8/26 3:05 AM, Dapeng Wang wrote:
Following up on Tom's suggestion that Chapters 2 and 3 of the
tutorial likewise lack introductory paragraphs, I've attached a
patch that adds them.
Thanks for the contribution!
In the future use "Reply all" and figure out why your email client did
not add a proper Reply-To header.
--
Andreas Karlsson
Percona
Thanks Andreas! Noted - I didn't have the original thread
in my mailbox at the time, but I'm subscribed now so future
replies will thread properly.
Regards,
Dapeng Wang
Andreas Karlsson <andreas@proxel.se> 于2026年4月9日周四 20:55写道：
Show quoted text
On 4/8/26 3:05 AM, Dapeng Wang wrote:
Following up on Tom's suggestion that Chapters 2 and 3 of the
tutorial likewise lack introductory paragraphs, I've attached a
patch that adds them.Thanks for the contribution!
In the future use "Reply all" and figure out why your email client did
not add a proper Reply-To header.--
Andreas Karlsson
Percona
On 4/10/26 2:36 AM, Dapeng Wang wrote:
Thanks Andreas! Noted - I didn't have the original thread
in my mailbox at the time, but I'm subscribed now so future
replies will thread properly.
I see! Then the general recommendation is to use the re-send email
button in our mailing list archives. I know it was buggy some time ago
but I think it has been fixed now.
Andreas
Good to know, thanks! I'll use the resend email button next time.
Andreas Karlsson <andreas@proxel.se> 于2026年4月10日周五 08:40写道：
Show quoted text
On 4/10/26 2:36 AM, Dapeng Wang wrote:
Thanks Andreas! Noted - I didn't have the original thread
in my mailbox at the time, but I'm subscribed now so future
replies will thread properly.I see! Then the general recommendation is to use the re-send email
button in our mailing list archives. I know it was buggy some time ago
but I think it has been fixed now.Andreas
Andreas Karlsson <andreas@proxel.se> writes:
On 4/10/26 2:36 AM, Dapeng Wang wrote:
Thanks Andreas! Noted - I didn't have the original thread
in my mailbox at the time, but I'm subscribed now so future
replies will thread properly.
I see! Then the general recommendation is to use the re-send email
button in our mailing list archives. I know it was buggy some time ago
but I think it has been fixed now.
Yeah, I use that all the time when I want to reply to some old
thread that I no longer have locally. It's been flaky once or
twice for me, but normally it works fine.
A more pressing problem is that this iteration of the thread
isn't attached to the CF entry; you need to do that so that
it shows up as having current traffic. Right now,
https://commitfest.postgresql.org/patch/6506/
still shows the 19-Feb patch as current.
regards, tom lane
Done - I've attached the new thread to the CF entry.
Regards,
Dapeng Wang
Tom Lane <tgl@sss.pgh.pa.us> 于2026年4月10日周五 08:47写道：
Show quoted text
Andreas Karlsson <andreas@proxel.se> writes:
On 4/10/26 2:36 AM, Dapeng Wang wrote:
Thanks Andreas! Noted - I didn't have the original thread
in my mailbox at the time, but I'm subscribed now so future
replies will thread properly.I see! Then the general recommendation is to use the re-send email
button in our mailing list archives. I know it was buggy some time ago
but I think it has been fixed now.Yeah, I use that all the time when I want to reply to some old
thread that I no longer have locally. It's been flaky once or
twice for me, but normally it works fine.A more pressing problem is that this iteration of the thread
isn't attached to the CF entry; you need to do that so that
it shows up as having current traffic. Right now,https://commitfest.postgresql.org/patch/6506/
still shows the 19-Feb patch as current.
regards, tom lane