Horton

Re: Schema variables - new implementation for Postgres 15

Peter Eisentraut <peter@eisentraut.org>

View thread
From: Peter Eisentraut <peter@eisentraut.org>
To: Pavel Stehule <pavel.stehule@gmail.com>, walther@technowledgy.de
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Dmitry Dolgov <9erthalion6@gmail.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Sergey Shinderuk <s.shinderuk@postgrespro.ru>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Julien Rouhaud <rjuju123@gmail.com>, dean.a.rasheed@gmail.com, er@xs4all.nl, joel@compiler.org, pgsql-hackers@lists.postgresql.org
Date: 2024-06-02T21:31:03Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow underscores in integer and numeric constants.

  2. Remove special outfuncs/readfuncs handling of RangeVar.catalogname.

  3. Remove extra space from dumped ALTER DEFAULT PRIVILEGES.

  4. Create FKs properly when attaching table as partition

  5. psql: improve tab-complete's handling of variant SQL names.

On 25.05.24 12:50, Pavel Stehule wrote:
> It looks odd - It is not intuitive, it introduces new inconsistency 
> inside Postgres, or with solutions in other databases. No other database 
> has a similar rule, so users coming from Oracle, Db2, or MSSQL, Firebird 
> will be confused. Users that use PL/pgSQL will be confused.

Do you have a description of what those other systems do?  Maybe you 
posted it already earlier?