Re: regdatabase
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: nathandbossart@gmail.com, pgsql-hackers@postgresql.org
Date: 2025-05-06T23:45:15Z
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 →
-
Add new OID alias type regdatabase.
- bd09f024a1bb 19 (unreleased) landed
-
pg_upgrade: Preserve database OIDs.
- aa01051418f1 15.0 cited
On Wed, May 07, 2025 at 07:28:02AM +0900, Tatsuo Ishii wrote: > I think regdatabase is a good idea. I've also found your reference from the lists of 2019 to be the only one referring to a regdatabase. If it means that I will type less by not having to do joins with pg_database, count me in. The last time I recall we've discussed about a reg shortcut was regcollation, which was mentioned as useful for dumps. Even if we've finished by not using it in the dump, I tend to find these shortcuts always useful. For regdatabase, there would be at least two simplications related to the dump of subscriptions, where we could switch the queries to the new grammar for backend versions able to support the new grammar, meaning that we could remove entirely these parts in 11~12 years once the versions that do not support the new reg shortcut would be out of scope. :D -- Michael