Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wjBwo-000bvW-1J for pgsql-docs@arkaria.postgresql.org; Mon, 13 Jul 2026 08:23:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wjBwm-008zZd-2k for pgsql-docs@arkaria.postgresql.org; Mon, 13 Jul 2026 08:23:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wiwkp-0073eQ-0U for pgsql-docs@lists.postgresql.org; Sun, 12 Jul 2026 16:10:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wiwkn-00000000LTZ-0shQ for pgsql-docs@lists.postgresql.org; Sun, 12 Jul 2026 16:10:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=j/YvnvQ80ODI9fpFZtnm7v1iXgmOB5JIu5o+SFl9v6A=; b=63HVI3DSyj6EKWAUEDVfc3U+tz S3r6n6NJ2X/+Qd+EKHqC2RU3Wgthsd5Pl0HEF1W4wSVAQk+p4frAnebtqaRY+CUsyOKUjhGD37yiq ivyf5J0riNRAz3iLXnO/z9GS+Ql33vIcelJ963hnO3BonO3byKrsmr+WNUc/deacOprMLHz1fjHmZ idM21QxCBo+JssLkYELcdKJaf/SqK3YEHGBPOszSRIIeYRV8dOOPss32gbny8iov7L64YSpq2O7Pk bd68x3/36rUj+lUJ8UKSFPwcB/5bXnAViNVhWuFDE27uM8z516+lkFg/ZCSa6En292SYjY+LAWlRm GVrzpenw==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wiwkm-0019eh-2k for pgsql-docs@lists.postgresql.org; Sun, 12 Jul 2026 16:10:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wiwkj-006IMC-0z for pgsql-docs@lists.postgresql.org; Sun, 12 Jul 2026 16:10:02 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Suggestion to improve PostgreSQL documentation clarity To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: bilalabdulkadir286@gmail.com Reply-To: bilalabdulkadir286@gmail.com, pgsql-docs@lists.postgresql.org Date: Sun, 12 Jul 2026 16:09:34 +0000 Message-ID: <178387257473.881000.14948160238963995239@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/source-format.html Description: Hello PostgreSQL Documentation Team, I am a PostgreSQL learner and community member. While studying PostgreSQL documentation and working on database projects, I found that some sections could benefit from additional beginner-friendly explanations and practical examples. I suggest adding more step-by-step examples for new users, especially around database setup, connection configuration, user privileges, security settings, and common migration workflows. Clear examples showing real-world scenarios would help learners and developers understand PostgreSQL concepts more easily and reduce confusion when applying the documentation in practice. Thank you for maintaining excellent PostgreSQL documentation and for considering this suggestion. Best regards, Bilal Abdulkadir Muhammed