Re: Schema variables - new implementation for Postgres 15
Julien Rouhaud <rjuju123@gmail.com>
From: Julien Rouhaud <rjuju123@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>, Joel Jacobson <joel@compiler.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-01-22T04:04:01Z
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 →
-
Allow underscores in integer and numeric constants.
- faff8f8e47f1 16.0 cited
-
Remove special outfuncs/readfuncs handling of RangeVar.catalogname.
- 3cece34be842 16.0 cited
-
Remove extra space from dumped ALTER DEFAULT PRIVILEGES.
- 2af33369e794 16.0 cited
-
Create FKs properly when attaching table as partition
- b0284bfb1db5 16.0 cited
-
psql: improve tab-complete's handling of variant SQL names.
- 02b8048ba5dc 15.0 cited
Hi, On Fri, Jan 21, 2022 at 09:23:34PM +0100, Pavel Stehule wrote: > > st 19. 1. 2022 v 9:01 odesílatel Julien Rouhaud <rjuju123@gmail.com> napsal: > > > > Also, the pg_dump handling emits a COLLATION option for session variables > > even > > for default collation, while it should only emit it if the collation is > > not the > > type's default collation. As a reference, for attributes the SQL used is: > > > > "CASE WHEN a.attcollation > > <> t.typcollation " > > "THEN a.attcollation ELSE > > 0 END AS attcollation,\n" > > > > Isn't it a different issue? I don't see filtering DEFAULT_COLLATION_OID in > pg_dump code. But this case protects against a redundant COLLATE clause, > and for consistency, this check should be done for variables too. Yes, sorry my message was a bit ambiguous as for all native collatable types the "default" collation is the type's default collation, I thought that the code extract would make it clear enough. In any case your fix is exactly what I had in mind so it's perfect, thanks! > I am sending updated patches Thanks a lot! I will try to review them over the weekend.