[PATCH] Improvements to "Getting started" tutorial for Google Code-in task

From: LAM JUN RONG <h1710074(at)nushigh(dot)edu(dot)sg>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: [PATCH] Improvements to "Getting started" tutorial for Google Code-in task
Date: 2018-11-02 13:07:50
Message-ID: SG2PR01MB22991C748D58EB6D1CA7E11AA0CF0@SG2PR01MB2299.apcprd01.prod.exchangelabs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I’m a student taking part in Google Code-in 2018. The<http://Code-in 2018. The> task I am currently working on, https://codein.withgoogle.com/dashboard/task-instances/6406170207059968/, requires that I review and improve the “Getting Started” tutorial in the PostgreSQL docs, and submit a patch to this mailing list.

After reviewing the documentation, I found some parts to be slightly unclear. For example, in section 1.3 on creating databases, I found “no response” a bit unclear or ambiguous, so I replaced it with “exit without any error messages”.

After some experimentation, I found that a part of the documentation was incorrect. In Section 1.3, it was stated that “Database names must have an alphabetic first character”. However, I was able to create databases with names like “1234”, “$” or even “😀😀”. Hence, I decided to remove that sentence.

A diff of my changes is attached.

Thank you and I would appreciate any feedback that would make my first Postgres patch better!

Jun Rong

Attachment Content-Type Size
GCI-pgsql-docs.diff text/plain 5.8 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-11-02 13:11:45 Re: zheap: a new storage format for PostgreSQL
Previous Message Jesper Pedersen 2018-11-02 13:07:25 Re: pread() and pwrite()