Date: Thu, 4 Jun 2026 11:35:48 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Sergey Shinderuk <s.shinderuk@postgrespro.ru>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19509: Typo in 19 beta release notes (debug_print_parse)
Message-ID: <aiGbVLpc-_hvULUl@momjian.us>
References: <19509-2a8a94637d323f44@postgresql.org>
 <fe265985f29c072174e51da3b53691f207cbb82a.camel@postgrespro.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <fe265985f29c072174e51da3b53691f207cbb82a.camel@postgrespro.ru>
Archived-At: 
 <https://www.postgresql.org/message-id/aiGbVLpc-_hvULUl%40momjian.us>
Precedence: bulk

On Thu, Jun  4, 2026 at 06:22:33PM +0300, Sergey Shinderuk wrote:
> On Thu, 2026-06-04 at 14:55 +0000, PG Bug reporting form wrote:
> > The following bug has been logged on the website:
> > 
> > Bug reference:      19509
> > Logged by:          Sergey Shinderuk
> > Email address:      s.shinderuk@postgrespro.ru
> > PostgreSQL version: 19beta1
> > Operating system:   Debian GNU/Linux 13 (trixie)
> > Description:        
> > 
> > Good day,
> > 
> > I've found a typo in 19 beta release notes:
> > https://www.postgresql.org/docs/19/release-19.html#RELEASE-19-MONITORING
> > 
> > > Add server variable debug_print_parse to log the raw parse tree
> > > (Chao Li)
> > 
> > Should be debug_print_raw_parse.
> > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=06473f5a3
> > 
> > Best regards,
> > Sergey
> > 
> 
> 
> Two more:
> 
> > Add server-side report for SNI (Server Name Indication) (Daniel
> Gustafsson, Jacob Champion)
> 
> s/report/support/

Thanks, will fix.

> > Allow CREATE SCHEMA to create more types of non-schema objects
> (Kirill Reshke, Jian He, Tom Lane)
> 
> s/non-schema/schema/

I think the existing wording is right.  This is about creating schema
elements inside of schemas:

       CREATE SCHEMA schema_name [ AUTHORIZATION role_specification ] [ schema_element [ ... ] ]

       schema_element
           An SQL statement defining an object to be created within the
           schema. Currently, only CREATE AGGREGATE, CREATE COLLATION,
           CREATE DOMAIN, CREATE FUNCTION, CREATE INDEX, CREATE OPERATOR,
           CREATE PROCEDURE, CREATE SEQUENCE, CREATE TABLE, CREATE TEXT
           SEARCH CONFIGURATION, CREATE TEXT SEARCH DICTIONARY, CREATE TEXT
           SEARCH PARSER, CREATE TEXT SEARCH TEMPLATE, CREATE TRIGGER,
           CREATE TYPE, CREATE VIEW, and GRANT are accepted as clauses
           within CREATE SCHEMA. Other kinds of objects may be created
           within the schema in separate commands after the schema
           is created.

I have reworded it to be:

   Allow CREATE SCHEMA to create more types of objects in newly-created
   schemas (Kirill Reshke, Jian He, Tom Lane)

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.