| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | nathandbossart(at)gmail(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: regdatabase |
| Date: | 2025-05-06 22:28:02 |
| Message-ID: | 20250507.072802.141594448236275664.ishii@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Every once in a while, I find myself wanting to use regdatabase for
> something like current_database()::regdatabase, and I'm always surprised
> when I inevitably rediscover that it doesn't exist. I only found one
> reference to the idea in the archives [0]. So, I have two questions:
>
> * Is there an easier way to get the current database's (or any database's)
> OID that I am overlooking (besides "SELECT oid FROM pg_database...")?
I always do "SELECT oid FROM pg_database...". I have no idea other way.
> * Would anyone object if I put together some patches to add regdatabase?
I think regdatabase is a good idea.
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-05-06 23:00:39 | Re: Large expressions in indexes can't be stored (non-TOASTable) |
| Previous Message | Shayon Mukherjee | 2025-05-06 22:05:42 | Prolonged truncation phase during vacuum on toast table with repeated interruptions by lock waiters and a proposed POC patch |